Smart table system utilizing extended reality

ABSTRACT

Systems, methods and computer-readable storage media including an interactive surface including a touchscreen and a plurality of interactive surface sensor devices, a plurality of smart headsets including a transparent display and a plurality of smart headset sensor devices, each of the smart headsets configured to be respectively worn by an individual, and a processing circuit configured to generate graphical user interfaces for each of the smart headsets. The processing circuit is further configured to provide the graphical user interfaces to each of the smart headsets. The processing circuit is further configured to receive sensor device data. The processing circuit is further configured to update, in response to receiving the sensor device data, a first graphical user interface for a first smart headset. The processing circuit is further configured to update a second graphical user interface for a second smart headset.

TECHNICAL FIELD

This application relates generally to the use of a smart table toimprove efficiency and ease of conducting transactions at a providerlocation associated with a provider. More specifically, this applicationrelates to systems and methods for using smart display tables and smartglasses for content customization of shared multi-dimensional graphicaluser interfaces.

BACKGROUND

Customers of a provider are able to access a variety of services throughsoftware applications, such as mobile applications on user devices, toperform various tasks. For example, customers may use aninternet-enabled application to conduct transactions, change settings,and carry out other actions related to a customer account or withrespect to a product offered by the provider. However, certaintransactions and tasks may require a customer to visit a providerlocation (e.g., due to security, needing to meet with a providerrepresentative).

SUMMARY

Some embodiments relate to a smart table system. The smart table systemcan include an interactive surface that can include a touchscreen and aplurality of interactive surface sensor devices. Further, the smarttable system can include plurality of smart headsets that can include atransparent display and a plurality of smart headset sensor devices,each of the smart headsets configured to be respectively worn by anindividual. Further, the smart table system can include a processingcircuit, the processing circuits configured to generate graphical userinterfaces for each of the smart headsets. Further, the processingcircuit can be configured to provide the graphical user interfaces toeach of the smart headsets. Further, the processing circuit can beconfigured to receive sensor device data associated with at least one ofbiological data, behavioral data, or a user input from at least one ofthe plurality of interactive surface sensor devices or the plurality ofsmart headset sensor devices. Further, the processing circuit can beconfigured to update, in response to receiving the sensor device data, afirst graphical user interface for a first smart headset of the smartheadsets based on the sensor device data, wherein the first graphicaluser interface is unique to the first smart headset and is worn by afirst individual and update, in response to receiving the sensor devicedata, a second graphical user interface for a second smart headset ofthe smart headsets based on the sensor device data, and wherein thesecond graphical user interface is unique to the second smart headsetand is worn by a second individual different than the first individual.

In some embodiments, each of the graphical user interfaces is configuredto display content that is unique to each of the smart headsets and isbased on at least on one of a user preference or the sensor device dataand the user preference can include size and color parameters of a user,and wherein the processing circuit is configured to adjust contentdisplayed on each of the graphical user interfaces. In variousembodiments, the processing circuit can be configured to continuouslyupdate each of the graphical user interfaces in real-time, the graphicaluser interfaces including a combination of a set of views includingcontent based on the sensor device data, wherein each of the set ofviews can include a subset of views and the set of views can include atable view and a plurality of smart headset views, and the subset ofviews comprises a customer view, a provider view, and a manager view,and wherein each of the subset of views can include different contentunique to the individual. In some embodiments, the processing circuitcan be further configured to receive, from a microphone, sound inputfrom a customer, wherein the customer is the first individual, updatethe first graphical user interface of the first smart headset of thesmart headsets based on the sound input, wherein the update can includeupdating first content of the first graphical user interface, and updatethe second graphical user interface of the second smart headset of thesmart headsets based on the sound input, wherein the update can includeupdating second content of the second graphical user interface differentfrom the first content. In various embodiments, the smart table systemcan further include a mobile device associated with a customer, whereinthe customer is the first individual, the mobile device can beconfigured to communicate over a network with a network circuit of thesmart table system and to provide authentication information of thecustomer to the network circuit, wherein the authentication informationis at least one of a customer password, biometric data, or geometricinformation. In some embodiments, the biological data, the behavioraldata, or the user input is indicative of at least one of a usersentiment, a user emotion, a user attentiveness, a user gesture, or auser preference.

Another example embodiment relates to a smart table system. The smarttable system can include a plurality of devices including a camera, amicrophone, and a stress sensor, each device configured to collect firstdevice data. Further, the smart table system can include a plurality ofsmart headsets including a transparent display and coupled to aplurality of smart headset devices, the smart headset devices configuredto collect second device data, wherein the second device data is smartheadset device data, and each of the smart headsets configured to beworn by an individual. Further, the smart table system can include aninteractive surface including a touchscreen and a processing circuitconfigured to generate graphical user interfaces for each of the smartheadsets. Further, the processing circuit can be configured to providethe graphical user interfaces to a respective smart headset. Further,the processing circuit can be configured to update a first graphicaluser interface of the graphical user interfaces for a first smartheadset of the smart headsets based on the first device data and thesecond device data, update a second graphical user interface of thegraphical user interfaces for a second smart headset of the smartheadsets based on the first device data and the second device data, andwherein the first graphical user interface is unique to the first smartheadset and is worn by a first individual, and wherein the secondgraphical user interface is unique to the second smart headset and isworn by a second individual different than the first individual.

In some embodiments, each of the graphical user interfaces is configuredto display content that is unique to each of the smart headsets and isbased on at least one of a user preference, the first device data, orthe second device data. In various embodiments, the processing circuitis configured to continuously update each of the graphical userinterfaces in real-time, the graphical user interfaces can include acombination of a set of views including content based on the firstdevice data and the second device data, wherein each of the set of viewsincludes a subset of views. In some embodiments, the smart table systemcan further include a mobile device associated with a customer, whereinthe customer is the first individual, the mobile device configured tocommunicate over a network with a network circuit of the smart tablesystem, and configured to provide authentication information of thecustomer to the network circuit, wherein the authentication informationis at least one of a customer password, biometric data, or geometricinformation.

An additional example embodiment relates to a smart system. The smarttable system can include an interactive surface including a touchscreenand a plurality of interactive surface sensors. Further, the smart tablesystem can include a plurality of smart headsets including a transparentdisplay and a plurality of smart headset sensors, each of the smartheadsets configured to be worn by an individual and a processing circuitconfigured to generate graphical user interfaces for each of the smartheadsets. Further, the processing circuit can be configured to providethe graphical user interfaces to each of the smart headsets. Further,the processing circuit can be configured to receive sensor dataassociated with at least one of biological data, behavioral data, or auser input from at least one of the plurality of interactive surfacesensors or the plurality of smart headset sensors. Further, theprocessing circuit can be configured to in response to receiving thesensor data, update a first graphical user interface for a first smartheadset of the smart headsets based on the sensor data, wherein thefirst graphical user interface is unique to the first smart headset andis worn by a first individual, and in response to receiving the sensordata, update a second graphical user interface for a second smartheadset of the smart headsets based on the sensor data, and wherein thesecond graphical user interface is unique to the second smart headsetand is worn by a second individual different than the first individual.

In some embodiments, each of the graphical user interfaces is configuredto display content that is unique to each of the smart headsets and isbased on at least on one of a user preference or the sensor data and theuser preference can include size and color parameters of a user, andwherein the processing circuit is configured to adjust content displayedon each of the graphical user interfaces

In various embodiments, the processing circuit is configured tocontinuously update each of the graphical user interfaces in real-time,the graphical user interfaces can include a combination of a set ofviews including content based on the sensor data, wherein each of theset of views includes a subset of views, and the set of views caninclude a table view and a plurality of smart headset views, and thesubset of views can include a customer view, a provider view, and amanager view, and wherein each of the set of views and each of thesubset of views can include different content unique to the individual.In some embodiments, the processing circuit is further configured toreceive, from a microphone, sound input from a customer, wherein thecustomer is the first individual, update the first graphical userinterface of the first smart headset of the smart headsets based on thesound input, wherein the update can include updating content of thefirst graphical user interface, and update the second graphical userinterface of the second smart headset of the smart headsets based on thesound input, wherein the update can include updating second content ofthe second graphical user interface different from the first content. Invarious embodiments, the smart system can further include a mobiledevice associated with a customer, wherein the customer is the firstindividual, the mobile device configured to communicate over a networkwith a network circuit of the smart table system and configured toprovide authentication information of the customer to the networkcircuit, wherein the authentication information is at least one of acustomer password, biometric data, or geometric information. In someembodiments, the biological data, the behavioral data, or the user inputis indicative of at least one of a user sentiment, a user emotion, auser attentiveness, a user gesture, or a user preference.

These and other features, together with the organization and manner ofoperation thereof, will become apparent from the following detaileddescription when taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram of a smart table system including a providercomputing system and a smart table, according to example embodiments.

FIG. 1B is a block diagram illustrating an example computing systemsuitable for use in the example embodiments described herein.

FIG. 2A is a block diagram of the smart table of FIG. 1A, according toexample embodiments.

FIG. 2B is a block diagram of the smart headsets of FIG. 1A, accordingto example embodiments.

FIG. 3 is a flow diagram of a method for initiating a session with thesmart table of FIG. 1A, according to example embodiments.

FIG. 4 is an illustration of various configurations of the smart tableof FIG. 1A, according to example embodiments.

FIG. 5 is an illustration of additional configurations of the smarttable of FIG. 1A, according to example embodiments.

FIG. 6 is an illustration of a user interface of the smart table andpaired user devices of FIG. 1A, according to example embodiments.

FIG. 7 is an illustration of a user interface of the smart table of FIG.1A configured to receive an input from a customer or providerrepresentative, according to example embodiments.

FIG. 8 is an illustration of the smart table of FIG. 1A including adispensing mechanism, according to example embodiments.

FIG. 9 is an illustration of various user interface orientationsdisplayable by the smart table of FIG. 1A, according to exampleembodiments.

FIG. 10 is an illustration of example user interfaces of the user deviceof FIG. 1A when the user device is paired to the smart table of FIG. 1A,according to example embodiments.

FIG. 11 is a flow diagram of a method for managing content with thesmart table and smart headsets of FIG. 1A, according to exampleembodiments.

FIG. 12 is an illustration of the smart table and smart headsets of FIG.1A including sensor devices in an environment, according to exampleembodiments.

FIGS. 13A-13B are illustrations of various individual views of the smartheadset of FIG. 1A, according to example embodiments.

FIGS. 14A-14B are illustrations of various individual views of the smartheadset of FIG. 1A, according to example embodiments.

FIGS. 15A-15B are illustrations of various individual views of the smartheadset of FIG. 1A, according to example embodiments.

FIGS. 16A-16B are illustrations of various individual views of the smartheadset of FIG. 1A, according to example embodiments.

FIGS. 17A-17F are illustrations of various individual views of the smartheadset of FIG. 1A, according to example embodiments.

FIG. 18 is an illustration of the smart table and smart headsets of FIG.1A in an environment, according to example embodiments.

It will be recognized that the figures are schematic representations forpurposes of illustration. The figures are provided for the purpose ofillustrating one or more embodiments with the explicit understandingthat they will not be used to limit the scope or the meaning of theclaims.

DETAILED DESCRIPTION

Referring generally to the figures, the systems and methods relategenerally to a smart table system and configuring content (e.g., sharedmulti-dimensional graphical user interface) on a plurality of userinteractive devices based on real-time environment analysis and specificpreferences of users. The content of the plurality of user interactivedevices can be specific to a user such that each user can be presentedunique content via a variety of views (e.g., customer, employee,manager, and so on). In some embodiments, the real-time environmentanalysis can include receiving sensor data (sometimes referred to hereinas “IoT device data”) from one or more sensors and updating content forone or more of the plurality of user interactive devices (e.g., smartheadset, smart table, and so on). In various embodiments, the contentcan further be magnified, highlighted, colored, bolded, variouslyemphasized, and/or variously manipulated to draw the attention of a userand/or notify the user.

In many embodiments, a computing device (e.g., desktop computer, mobiledevice, smart device) can present a variety of content (e.g., within theviewport of the computing device) that is universal to the viewers suchthat the viewers can view the presented variety of content jointly. Thatis, the ability to view content unique to a viewer within a viewport ofthe computing device, such as when one or more viewers are viewing thecomputing device, they view different content, provides computingdevices enhanced flexibility on how content is presented within theviewport of the computing device. This causal approach allows computingdevices to produce significant improvements to the engagement andnoticeability of content when presented through the viewport ofcomputing devices. Therefore, the smart table system addresses problemsin application development by providing an improved content managementtool for the production and presentation of content.

Accordingly, the present disclosure is directed to a smart table systemincluding systems and methods for configuring content based on theenvironment in which one or more users are present and sensors ofvarious computing devices (e.g., smart table, smart headsets, IoTdevices) within the environment. That is, the content viewed by aspecific user can be unique (e.g., user specific) to the specific userbased on environment data and sensor data associated with the specificuser. In some implementations, the described systems and methods involvegenerating and providing a shared multi-dimensional graphical userinterface (e.g., sometime referred to herein as a “multi-dimensionalgraphical user interface system”). The shared multi-dimensionalgraphical user interface enables a variety of computing devices to workin combination to present user specific content to one or more users.Providing the user specific graphical user interfaces within theviewport of the one or more computing devices leads to an improvement inthe human-machine interaction process as the user is provided withimproved control over the content. Furthermore, said user specificgraphical user interfaces can ensure, for example, that the content ispresented in a manner such that the user can understand, furtherimproving the end user experience. Additionally, the user specificgraphical user interfaces provides the end user with control over howthe content is executed, providing an improved user interface.

The present disclosure can also provide improvements to traditionalcomputing systems by providing a smart table system that can organizecontent on a graphical user interface based on the user preferences andenvironmental data (e.g., smart table, smart headsets, IoT devices,sensor data, and so on). Moreover, this technical solution enables smarttable systems to customize user experiences on particular devices toimprove engagement and noticeability of content when presented throughthe viewport of the computing device.

Therefore, aspects of the present disclosure also address problems incontent presentation by providing improved presentation technology forthe presentation of content on particular computer devices. Inparticular, the present disclosure addresses the technical challenges ininterfacing by presenting personalized content. Moreover, the userspecific graphical user interfaces that are provided based on sharingthe processing load across a variety of computing devices can saveprocessing power and other computing resources such as memory, reduceelectrical power consumption by the computing devices described hereinand reduce data transmissions via the computer network to reducebandwidth requirements and usage of the data processing system (e.g.,adapting to network traffic needs, leveraging storage on computingdevices and sharing content via local communications networks (e.g.,shared connection, Bluetooth™, NFC, and so on)).

Additionally, the present disclosure is directed to improvements of userinterfaces for electronic device, thus improving upon conventional userinterfaces to increase the efficiency of using electronic devices (e.g.,smart tables, smart headsets, mobile devices, and so on). For example,said user specific graphical user interfaces can display on the screentasks and indicators (e.g., icons, notifications, magnifications, and soon) that can be displayed and/or navigated to and displayed on variousdevices, such that the tasks and indicators display user specific dataand can enable data to be selected and adjusted. In another example, oneor more process circuits of the electronic devices can determine theamount of use (e.g., selected five times, utilized once, and so on) ofeach tasks and indicators over a period of time and determine how muchmemory has been allocated to various tasks and indicators over a periodof time (e.g., tracking memory usage during sessions and over a periodof a time) such that adjustments to the user interface can be done inreal-time (e.g., end high memory usage processes, allocate more memoryusage to certain processes, enable more memory for usage, and so on).Moreover, the present disclosure is directed to improvements of identityverification such that a user can be verified for sessions. For example,said identity verification can include provisioning a random code (e.g.,token) to a communication device of the user and receive correspondenceincluding authentication information (e.g., biometric data, token,geometric data) such that one or more processors of the provider cananalyze and authenticate the user (e.g., cross-reference a token vault,cross-reference biometric templates, cross-reference latitude andlongitude of known locations) for one or more sessions at the provider(e.g., automatically send a control signal to an input of the smarttable system to provide access to view user interfaces on a smartheadset and/or smart table).

Referring to FIG. 1A, a block diagram of a smart table system 100 isshown, according to potential embodiments. The smart table system 100(e.g., sometimes referred to herein as the “multi-dimensional graphicaluser interface system”) includes a provider computing system 102associated with a provider, such as a service provider, bank, orfinancial institution (FI). The smart table system 100 further includesone or more user devices (e.g., user device 104), one or more smarttables (e.g., smart table 106), and a branch computing system 108 (e.g.,a computing system of a branch location of the FI). In some embodiments,the provider computing system 102, user device 104 (as well as anyadditional user devices), smart table 106 (and any additional smarttables), IoT devices 190, smart headsets 195, and branch computingsystem 108 are directly communicably coupled. In some embodiments, thecomponents of smart table system 100 may be communicably and operativelycoupled to each other over a network, such as network 154, that permitsthe direct or indirect exchange of data, values, instructions, messages,and the like (represented by the double-headed arrows in FIG. 1A). Thenetwork 154 may include one or more of a cellular network, the Internet,Wi-Fi™, Wi-Max™, a proprietary provider network, a proprietary retail orservice provider network, and/or any other kind of wireless or wirednetwork.

Each system or device in smart table system 100 may include one or moreprocessors, memories, network interfaces (sometimes referred to hereinas a “network circuit”) and user interfaces. The memory may storeprogramming logic that, when executed by the processor, controls theoperation of the corresponding computing system or device. The memorymay also store data in databases. For example, memory 142 may storeprogramming logic that when executed by processor 140 within processingcircuit 138, causes employee database 144 to update information for anemployee account with communications received from a user device 104.The network interfaces (e.g., network interface 110 of providercomputing system 102, sometimes referred to herein as a “networkcircuit”) may allow the computing systems and devices to communicatewirelessly or otherwise. The various components of devices in smarttable system 100 may be implemented via hardware (e.g., circuitry),software (e.g., executable code), or any combination thereof. Devicesand components in FIG. 1A can be added, deleted, integrated, separated,and/or rearranged in various embodiments of the disclosure.

The provider computing system 102 may be managed by a provider, such asa credit card issuer, a consultant, a retailer, a service provider,and/or the like. The provider computing system 102 includes a networkinterface 110, a processing circuit 112, and an input/output device 122.The network interface 110 is structured and used to establishconnections with other computing systems and devices (e.g., the userdevices 104, the smart tables 106, the branch computing system 108,etc.) via the network 154. The network interface 110 includes programlogic that facilitates connection of the provider computing system 102to the network 154. For example, the network interface 110 may includeany combination of a wireless network transceiver (e.g., a cellularmodem, a Bluetooth™ transceiver, a WiFi™ transceiver, etc.) and/or awired network transceiver (e.g., an Ethernet transceiver). In somearrangements, the network interface 110 includes the hardware (e.g.,processor, memory, and so on) and machine-readable media sufficient tosupport communication over multiple channels of data communication.Further, in some arrangements, the network interface 110 includescryptography capabilities to establish a secure or relatively securecommunication session in which data communicated over the session isencrypted. In various embodiments, the smart table system 100 can adaptto network traffic needs by compressing content, by any computing devicedescribed herein, and sending it (e.g., via network 154) to variousother computing devices, by adjusting security filters to remove junktraffic off network 154 (e.g., by monitoring packets), and so on.

The processing circuit 112 includes a processor 114, a memory 116, and aprovider client application 120. The memory 116 may be one or moredevices (e.g., RAM, ROM, Flash memory, hard disk storage) for storingdata and/or computer code for completing and/or facilitating the variousprocesses described herein. The memory 116 may be or includenon-transient volatile memory, non-volatile memory, and non-transitorycomputer storage media. Memory 116 may include database components,object code components, script components, or any other type ofinformation structure for supporting the various activities andinformation structures described herein. Memory 116 may be communicablycoupled to the processor 114 and include computer code or instructionsfor executing one or more processes described herein. The processor 114may be implemented as one or more application specific integratedcircuits (ASICs), field programmable gate arrays (FPGAs), a group ofprocessing components, or other suitable electronic processingcomponents. As such, the provider computing system 102 is configured torun a variety of application programs and store associated data in adatabase of the memory 116 (e.g., customer account database 118). Onesuch application may be the provider client application 120.

The memory 116 may store a customer account database 118, according tosome embodiments. The customer account database 118 may be configured tostore updated personal information for customer accounts associated withthe provider (e.g., the FI). For example, the customer account database118 saves personal user information, such as name, age, gender, address,education, occupation, etc., customer preferences, such as notificationpreferences, security preferences, etc., and authentication information,such as customer passwords, biometric data for the customer, geometricinformation (e.g., latitude, longitude), etc. In some embodiments, thecustomer account database 118 includes a token vault that stores anassociated customer token and/or device token for each customer account.The customer account database 118 may further be configured to storefinancial data for each customer account, such as past transactions,different provider account information (e.g., balances, debt, type ofaccount, etc.), investments, loans, mortgages, and so on.

In some embodiments, the provider client application 120 may beincorporated with an existing application in use by the providercomputing system 102 (e.g., a mobile provider application, a serviceprovider application, etc.). In other embodiments, the provider clientapplication 120 is a separate software application implemented on theprovider computing system 102. The provider client application 120 maybe downloaded by the provider computing system 102 prior to its usage,hard coded into the memory 116 of the provider computing system 102, orbe a network-based or web-based interface application such that theprovider computing system 102 may provide a web browser to access theapplication, which may be executed remotely from the provider computingsystem 102. Accordingly, the provider computing system 102 may includesoftware and/or hardware capable of implementing a network-based orweb-based application. For example, in some instances, the providerclient application 120 includes software such as HTML, XML, WML, SGML,PHP (Hypertext Preprocessor), CGI, and like languages.

In the latter instance, a user (e.g., a provider employee) may log ontoor access the web-based interface before usage of the application. Inthis regard, the provider client application 120 may be supported by aseparate computing system (e.g., user device 104) including one or moreservers, processors, network interface (sometimes referred to herein asa “network circuit”), and so on, that transmit applications for use tothe provider computing system 102.

In certain embodiments, the provider client application 120 includes anapplication programming interface (API) and/or a software developmentkit (SDK) that facilitate the integration of other applications with theprovider client application 120. For example, the provider clientapplication 120 is configured to utilize the functionality of the branchcomputing system 108 by interacting with the branch client application150 through an API.

Still referring to FIG. 1A, the input/output device 122 is structured toreceive communications from and provide communications to provideremployees associated with the provider computing system 102. Theinput/output device 122 is structured to exchange data, communications,instructions, etc. with an input/output component of the providercomputing system 102. In one embodiment, the input/output device 122includes communication circuitry for facilitating the exchange of data,values, messages, and the like between the input/output device 122 andthe components of the provider computing system 102. In yet anotherembodiment, the input/output device 122 includes machine-readable mediafor facilitating the exchange of information between the input/outputdevice and the components of the provider computing system 102. In yetanother embodiment, the input/output device 122 includes any combinationof hardware components, communication circuitry, and machine-readablemedia.

In some embodiments, the input/output device 122 includes suitableinput/output ports and/or uses an interconnect bus (not shown) forinterconnection with a local display (e.g., a touchscreen display)and/or keyboard/mouse devices (when applicable), or the like, serving asa local user interface for programming and/or data entry, retrieval, orother user interaction purposes. As such, the input/output device 122may provide an interface for the user to interact with variousapplications (e.g., the provider client application 120) stored on theprovider computing system 102. For example, the input/output device 122includes a keyboard, a keypad, a mouse, joystick, a touch screen, amicrophone, a biometric device, a virtual reality headset, smartglasses, smart headsets, and the like. As another example, input/outputdevice 122, may include, but is not limited to, a television monitor, acomputer monitor, a printer, a facsimile, a speaker, and so on. As usedherein, virtual reality, augmented reality, and mixed reality may eachbe used interchangeably yet refer to any kind of extended reality,including virtual reality, augmented reality, and mixed reality.

The branch computing system 108 similarly includes a network interface136, a processing circuit 138, and an input/output device 152. Thenetwork interface 136, the processing circuit 138, and the input/outputdevice 152 may function substantially similar to and include the same orsimilar components as the components of provider computing system 102,such as the network interface 110, the processing circuit 112, and theinput/output device 122, described above. As such, it should beunderstood that the description of the network interface 110, theprocessing circuit 112, and the input/output device 122 of the providercomputing system 102 provided above may be similarly applied to thenetwork interface 136, the processing circuit 138, and the input/outputdevice 152 of the branch computing system 108.

For example, the network interface 136 is similarly structured and usedto establish connections with other computing systems (e.g., theprovider computing system 102, the user devices 104, and/or the smarttables 106) via the network 154. The network interface 136 may furtherinclude any or all of the components discussed above, with reference tothe network interface 110.

The processing circuit 138 similarly includes a processor 140 and amemory 142. The processor 140 and the memory 142 are substantiallysimilar to the processor 114 and the memory 116 described above, withreference to the provider computing system 102. In some embodiments, thememory 142 includes an employee database 144 and a smart table database146. The employee database 144 may be structured to store dataconcerning each employee associated with the branch location. In someembodiments, the employee database 144 may store data regarding anidentification number, a job position, authorization information,contact information, a schedule, customer history, work history, anassociated user device 104, credentials, and so forth, of an employeethat works at the branch location associated with the branch computingsystem 108. For example, the employee database 144 may save biometricinformation (e.g., a fingerprint scan, an eye scan, a voice memo, etc.)and a password (e.g., PIN, alphanumeric code, QR code, barcode, etc.)for each employee at the branch location. As another example, theemployee database 144 stores security and data access rights for eachemployee that are utilized in conducting particular transactions(high-risk transactions, transactions with high-confidentialitycustomers, etc.).

Additionally, the employee database 144 may include the types oftrainings each employee has received, the clearances (e.g., access) thateach employee has obtained, a trustworthiness score for each employee,and any other pertinent information pertaining to each employee that maybe used to determine the employees qualifications for performing varioustransactions and other tasks using a smart table 106.

The smart table database 146 may be structured to store data for eachsmart table 106 at the branch location. The smart table database 146 maysave information regarding an identification number of each smart table106, service history information (e.g., a last date a smart table wasserviced for repairs and/or updates), transaction history information(e.g., number of customers that used the smart table 106), schedulinginformation (e.g., customers assigned to the smart table 106 for anupcoming smart table provider session, and/or power status (e.g.,charging, operating on a low battery level, etc.). For example, thesmart table database 146 may store a schedule of which customers will beusing a particular smart table 106 at the branch location. Beneficially,this may allow for branch managers to more effectively plan out smarttable provider sessions and decrease the likelihood of schedulingconflicts, such as two customers having conflicting sessions at the samesmart table 106.

The processing circuit 138 also is shown to include a smart tablemanagement circuit 148. In some embodiments, the smart table managementcircuit 148 is configured to receive new data (e.g., from the network154) relating to employees and smart tables 106 at a branch location.The smart table management circuit 148 may then update a correct,corresponding database (e.g., employee database 144 or smart tabledatabase 146). In some embodiments, the smart table management circuit148 is configured to receive requests from customers for an appointmentat a smart table 106. The smart table management circuit 148 may thenschedule the appointment based on what the client wants to accomplishduring the provider session (e.g., to ensure the assigned smart table106 has the necessary capabilities, such as a functional cash dispenser,credit card printer, check depositor, biometric authenticator, and soon) and the available smart tables 106 during a time slot desired by thecustomer.

The smart table management circuit 148 may also be configured toidentify which employees may be needed (e.g., based on experience and/oraccess) at a smart table 106 in order to conduct a planned transactionwith a customer during a provider session. For example, in generating arequest for a smart table provider session, a customer may be asked(e.g., via the user device 104 associated with the customer) what typeof transaction or provider task does the customer want to completeduring the smart table session. In some embodiments, the smart tablemanagement circuit 148 may generate and transmit a notification to userdevice 104 of an employee that a new smart table provider session,assigned to the employee, has been scheduled.

Although the employee database 144, smart table database 146, and smarttable management circuit 148 are shown as being a part of the branchcomputing system 108, these components may alternatively be a part ofthe provider computing system 102 and/or integrated into one or moresmart tables 106. In some embodiments, each of the provider computingsystem 102 and the branch computing system 108 may include acorresponding smart table management circuit the same as or similar tothe smart table management circuit 148.

The branch computing system 108 is similarly structured as the providercomputing system 102 to run a variety of application programs and storeassociated data in a database of the memory 142. One such applicationmay be the branch client application 150, for example.

The branch client application 150 may be substantially similar to theprovider client application 120, but may instead be tailored towardbranch employees or a branch manager at the branch location. Forexample, branch client application 150 is structured to generate userinterfaces to display on a smart table 106 to facilitate improvedcustomer experiences and employee interactions during an establishedprovider session. Particularly, the branch client application 150 isconfigured to communicate with the provider computing system 102, theuser devices 104 (e.g., customer user devices and employee userdevices), the IoT devices 190, the smart headsets 195, and smart tables106 to receive instructions or documents from the provider computingsystem 102 and/or the branch computing system 108 to complete specifictasks during a provider session at a smart table 106. Furthermore, thebranch client application 150 may be configured to communicate remindersto user devices 104 of employees regarding upcoming provider sessions ata smart table 106 and/or ongoing provider sessions at a smart table 106to perform a task associated with the provider session. For example, thebranch client application 150 may be configured to generate a reminderfor a branch employee to prepare a smart table 106 for an upcomingprovider session. Accordingly, the branch client application 150 iscommunicably coupled to the provider computing system 102 (e.g., throughinteractions with the provider client application 120), the user devices104 (e.g., through interactions with the user client application 132),and the smart tables 106 (e.g., through interactions with the smarttable client application 218 (FIG. 2A)).

The branch client application 150 may thus communicate with the providercomputing system 102, the user device 104, and the smart tables 106 toperform a variety of functions. For example, the branch clientapplication 150 is configured to reset a display of a smart table 106(e.g., reset a display to a generic welcome display or sleep modedisplay) at the end of a provider session with a customer. As such, thebranch client application 150 allows for a branch manager and branchemployees associated with the branch location to monitor and update userinterfaces of the smart tables 106 before, during, and after providersessions with one or more customers paired to one of the smart tables106.

The input/output device 152 may function substantially similarly to andinclude the same or similar components as the input/output device 122described above, with reference to the provider computing system 102.Accordingly, it will be understood that the description of theinput/output device 122 described above may also be applied to theinput/output device 152 of the branch computing system 108. As anexample, the input/output device 152 is similarly structured to receivecommunications from and provide communications to user devices 104 ofbranch employees and/or the branch manager associated with the branchcomputing system 108.

The smart table system 100 also includes one or more user devices 104,according to some embodiments. The user devices 104 may be a variety ofsuitable user computing devices. For example, the user devices 104 maycomprise mobile phones. In other embodiments, the user devices 104include personal computers (e.g., desktop computers or laptopcomputers), tablets, smart watches or other wearable devices (e.g.,rings, jewelry, headsets, bands), smart glasses, headphones, smartvehicle voice/touch command systems, virtual/augmented reality (VR/AR)systems (e.g., smart glasses, smart headsets), appliances, internet ofthings (IoT) devices, voice assistants, at-home touch screen displaysystems, and/or any other suitable user computing devices capable ofaccessing and communicating using local and/or global networks (e.g.,the network 154). The user devices 104 may be associated with employeesor with customers of the provider (e.g., customers at the FI). As such,the customer account database 118 may be further configured to storedevice information concerning each user device 104 associated with acustomer of the provider. Similarly, the employee database 144 may befurther configured to store device information pertaining to each userdevice 104 of an employee at a branch location. For example, the deviceinformation may include a device form (e.g., the type of user device104), a set of device capabilities (e.g., types of input/output devices,device mobility, operating system, installed applications, cameracapabilities, device communication capabilities, and so on), devicelocation information (e.g., geolocation data such as, latitude andlongitude information), and/or device identification and authenticationinformation (e.g., an encrypted device token for each user device 104,user authentication information, such as a PIN or biometric data,associated with each user device 104, etc.).

The user devices 104 may each similarly include a network interface 124,a processing circuit 126, and an input/output device 134. The networkinterface 124, the processing circuit 126, and the input/output device134 may be structured and function substantially similar to and includethe same or similar components as the network interface 110, theprocessing circuit 112, and the input/output device 122 described above,with reference to the provider computing system 102. Therefore, itshould be understood that the description of the network interface 110,the processing circuit 112, and the input/output device 122 of theprovider computing system 102 provided above may be similarly applied tothe network interface 124, the processing circuit 126, and theinput/output device 134 of each of the user devices 104.

In some embodiments, the network interface 124 is similarly structuredand used to establish connections with other computing systems (e.g.,the provider computing system 102, the branch computing system 108,other user devices 104, and the smart tables 106) via the network 154.The network interface 124 may further include any or all of thecomponents discussed above, with reference to the network interface 110.

The processing circuit 126 similarly includes a memory 130 and aprocessor 128. The memory 130 and the processor 128 are substantiallysimilar to the memory 116 and the processor 114 described above.Accordingly, the user devices 104 are similarly configured to run avariety of application programs and store associated data in a databaseof the memory 130 (e.g., user device database 131). For example, theuser devices 104 may be configured to run an application such as theuser client application 132 that is stored in the user device database131. In another example, the user devices 104 may be configured to storevarious user data, such as, but not limited to, personal user deviceinformation (e.g., names, addresses, phone numbers, contacts, call logs,installed applications, and so on), user device authenticationinformation (e.g., username/password combinations, device authenticationtokens, security question answers, unique client identifiers, biometricdata (such as digital representations of biometrics), geographic data,social media data, application specific data, and so on), and userdevice provider information (e.g., token information, account numbers,account balances, available credit, credit history, exchange histories,and so on) relating to the various accounts.

The user client application 132 may be substantially similar to theprovider client application 120, the branch client application 150, andthe smart table client application 218 (FIG. 2A), but may instead bespecifically tailored to the user associated with the user devices 104.For example, the user client application 132 is similarly structured toselectively provide displays and/or audio/visual communications to eachuser device 104 to allow for improved interactions between a customerand branch employees, branch managers, and provider employees.

Particularly, the user client application 132 is configured tocommunicate with the provider computing system 102, the branch computingsystem 108, and the smart tables 106 to facilitate user interactionswith a smart table 106 during a provider session at a branch location.As such, the user devices 104 are communicably coupled to the providercomputing system 102 (e.g., through interactions with the providerclient application 120), the branch computing system 108 (e.g., throughinteractions with the branch client application 150), and the smarttables 106 (e.g., through interactions with the smart table clientapplication 218 (FIG. 2A)).

The user client application 132 may therefore communicate with theprovider computing system 102, the smart tables 106, and the branchcomputing system 108 to perform a variety of functions. For example, theuser client application 132 is similarly configured to receive userinputs (e.g., via a user interface of the user device 104) to completeprovider interactions during a user session with a smart table 106,depending on whether the individual associated with the user device 104is an employee or a customer. Additionally, the user client application132 is configured to output information to a display of the user device104 regarding information on the provider interaction. For example, theuser client application 132 is configured to generate a user interfaceto show graphics regarding a financial history of a customer.

The user client application 132 is further configured to allow forcommunication with the provider client application 120 to allow a userassociated with the various user devices 104 to update accountinformation and/or provide feedback during a provider session with asmart table 106. Accordingly, the user client application 132facilitates effective communication with a branch manager, other branchemployees, the provider employees, and/or other customers (e.g., duringa provider session with two customers, such as a mother and daughter)during a connected session with a smart table 106.

The user client application 132 may also be structured to allow the userdevices 104 to retrieve and submit documents, forms, and/or any type ofnecessary information to and/or from a smart table 106 during anestablished session, as required to complete certain financial tasks. Insome instances, the user client application 132 may be configured toautomatically retrieve and/or submit documents, forms, or othernecessary information to and/or from a smart table 106 in response tothe establishment of a secure connection to the smart table 106. In someembodiments, the user client application 132 may be configured totemporarily store the various documents, forms, and/or necessaryinformation, which may then be selectively transmitted to the smarttable 106 in response to a user input from a customer or employee (e.g.,received via the input/output device 134).

In some embodiments, the user client application 132 may be configuredto temporarily store the various documents, forms, and/or necessaryinformation and then selectively transmit the various documents, forms,and/or necessary information to the smart table 106 in response to acustomer's arrival at a branch location. For example, the user device104 may automatically connect to the branch computing system 108 and/orthe one or more smart tables 106 when the user device 104 is withinrange of a network or communication device associated with the branchcomputing system 104 and/or the one or more smart tables 106.

In some embodiments, a customer or employee may identify various levelsof authority associated with each of the user devices 104. For example,in some implementations, a user may set a first user device 104 as aprimary user device and a second user device 104 as a secondary userdevice. In some instances, there may be various approved users of theuser devices 104, excluding the user, such as family members,caretakers, business partners for customers, or other branch employees,a branch manager, a supervising employee for employees at the branchlocation. As such, in some embodiments, a primary user device may havethe authority to veto or cancel the actions taken by a secondary userdevice.

Furthermore, the user client application 132 may be configured toprovide a device status for each user device 104 and/or each pair ofsmart headsets 195 to the provider session management circuit 210 (FIG.2A) of a smart table 106. The device status may include both a devicelocation and an indication of whether the respective user device 104and/or each pair of smart headsets 195 is active (e.g., turned on,connected to the internet, active notifications, within a specificdistance, communicating with a beacon, currently used, any combination,and so on). For example, the user client application 132 may beconfigured to automatically, periodically, and/or selectively providegeographical location information (e.g., latitude and longitude) to theprovider session management circuit 210. Additionally, the user clientapplication 132 may be configured to send the provider sessionmanagement circuit 210 a notification and/or an update when a given userdevice 104 is active.

In some embodiments, a user device 104 may be considered active if, forexample, the user device 104 is currently being used (e.g., by acustomer or by an employee during a provider session with a smart table106), a user has indicated that the provider computing system 102, thebranch computing system 108, and/or the smart tables 106 are permittedto send/retrieve data to/from the user device 104, and/or the userdevice 104 is within a predetermined distance from the branch computingsystem 108 or one of the smart tables 106. In some embodiments, theremay be additional manners in which the user device 104 may be consideredactive.

The input/output device 134 of each user device 104 may functionsubstantially similar to and include the same or similar components asthe input/output device 122 previously described, with reference to theprovider computing system 102. As such, it should be understood that thedescription of the input/output device 122 provided above may also beapplied to the input/output device 134 of each of the user devices 104.In some embodiments, the input/output device 134 of each user device 104is similarly structured to receive communications from and providecommunications to a user (e.g., customer or employee) associated withthe plurality of user devices 104.

For example, the input/output device 134 may include one or more userinterfaces, which may include one or more biometric sensors (such as aniris scanner, a fingerprint scanner, a heart monitor that identifiescardiovascular signals, etc.). The input/output device 134 may alsoinclude components that provide perceptible outputs (such as displaysand light sources for visually-perceptible elements, a speaker foraudible elements, and haptics for perceptible signaling via touch, etc.)and/or that permit the user to enter inputs (such as a stylus or forcesensor for detecting pressure on a display screen). One or more userdevices 104 may include one or more location sensors to allow the userdevices 104 to detect its location relative to other physical objects(e.g., a smart table 106 or other user devices) or geographic locations.Example location sensors may include global positioning system (GPS)devices and other navigation and geolocation devices, digital compasses,gyroscopes and other orientation sensors, as well as proximity sensorsor other sensors that permit the user device 104 to determine thepresence and relative distance of nearby devices, objects, and/orlocations.

Still referring to FIG. 1A, the smart table system 100 includes one ormore smart tables 106. The smart tables 106 may be tables of varyingsizes integrated with cash handling endpoints. Furthermore, the smarttables 106 may provide a shared graphical user interface for variousscenarios. In some embodiments, each of the smart tables 106 areassociated with a smart table identifier, such as a numeric oralphanumeric code, to identify the respective smart table to the branchcomputing system 108, the IoT devices 190, the smart headsets 195, theprovider computing system 102, and the user devices 104. For example, inresponse to walking into a lobby of a branch location for a scheduledprovider session, a user device 104 associated with the customer mayindicate to the customer which smart table 106 to go to in order toinitiate the session. While described with regards to a FI, the smarttables 106 may be used in other scenarios. For example, the smart tables106 may be used at a car dealership or car rental company, a hotel, abooking agent, and/or a medical office. The features of the smart tables106 are described in greater detail below, with reference to FIG. 2A.

The smart table system 100 can include one or more internet of thingsdevices 190 (collectively referred to herein as “IoT devices 190”),according to some embodiments. The IoT devices 190 can be disposed invarious locations within an area, according to some embodiments. The IoTdevices 190 can be configured within network 154 (e.g., wired and/orwireless network), according to some embodiments. The IoT devices 190can communicate data with various systems described herein. For example,the IoT devices 190 can include cameras that can communicate videographyand/or photography to the smart table 106 and/or smart headset 195. Inanother example, the IoT devices 190 can include a haptic sensor thatcan communicate force exerted by a user to the smart tables 106. Invarious implementations, the IoT devices 190 can be new or potentiallylegacy IoT devices 190 that are already in the building where the smarttable system 100 is located and/or integrated in computing devicesdescribed herein (e.g., IoT devices 410 and 510) such that the existinginfrastructure can be utilized.

Each IoT device can include one or more processors (e.g., any generalpurpose or special purpose processor), and can include and/or beoperably coupled to one or more transitory and/or non-transitory storagemediums and/or memory devices (e.g., any computer-readable storagemedia, such as a magnetic storage, optical storage, flash storage, RAM,etc.). In various implementations, one or more IoT Devices (e.g., of theIoT Devices 190) can be implemented as separate systems or integratedwithin a single system. The IoT devices 190 may be configured tocommunicate over network 154 via a variety of architectures (e.g.,client/server, peer-to-peer, etc.). The IoT devices 190 can beconfigured to provide a variety of interfaces for scene recognition(e.g., facial recognition, track movement, identify objects, adjustlight, adjust angles, and so on).

The IoT devices 190 can include, but are not limited to, any or all usermobile devices (phones, GPS devices), network enabled devices, acousticsensors, infrared (IR) counter sensors, cameras (e.g., of any wavelengthand including low resolution cameras, high resolution cameras, infrared,artificial intelligence cameras, etc.), radio-frequency identification(RFID) sensors, Bluetooth™ low energy (BLE) beacon sensors, near fieldcommunication (NFC) sensors, IP microphones, decibel meter, a passiveinfrared (PIR) sensors, infrared (IR) sensors, seismometers, barometers,relays, haptic sensors, touch screen sensors, electrooculography (EOG)sensors, electroencephalography (EEG) sensors, Wi-Fi™ triangulationsensors, geolocation sensors, pulse oximetry's (detect oxygen saturationof blood), altitude sensors, humidity sensors, magnetometers,accelerometers, gyroscopes, stress sensors (e.g., Galvanic Skin Response(GSR) sensor, sweat sensor, heart rate sensor, pulse wave sensor),desktop computers, laptops or notepad computers, mobile devices (e.g.,user devices 104) such as tablets or electronic pads, personal digitalassistants, smart phones, smart jewelry (e.g., ring, band, neckless),motion sensors, video gaming devices, virtual reality headsets, smartglasses (e.g., smart headsets 195), televisions or television auxiliaryboxes (also known as set-top boxes), kiosks, hosted virtual desktops, orany other such device capable of exchanging information via the network154.

The smart table system 100 can use a combination of different types ofIoT devices 190 connected within a network (or outside a network) (e.g.,network 154) to perform automatic scene recognition (e.g., facialrecognition, track movement, identify objects, adjust light, adjustangles, and so on). In various implementations, the IoT devices 190 canbe utilized to perform various tasks. For example, the cameras can beused for facial or cranial recognition, according to some embodiments.In various implementations, cameras can be used for general objectidentification (e.g. finding a person, finding a vehicle, scanningdocuments, authenticating individuals, and so on). In another example,the cameras can also be used to calculate the number of people in a roomand/or at a table, according to some embodiments. In yet anotherexample, the cameras, stress sensors, EEG sensors, EOG sensors, can beused to analyze people's gait or emotional state, according to someembodiments. In yet another example, the cameras can be used to identifydangerous objects (e.g., weapons, dangerous chemicals, etc.). In someimplementations, the IoT devices 190 can be used to assemble/createobjects from multiple photos and/or videos. The IR sensors can detectpeople in any light environment (e.g., bright light, dark light, etc.),according to some embodiments. The IR sensors, user devices 104, NFCsensors, cameras, PIR sensors, Wi-Fi™ triangulation sensors, can be usedto count people anonymously, or designate people by role (e.g., staff,visitors, vendors, student, manager, construction worker, manufacturerworker, etc.). The Wi-Fi™ triangulation sensor can be used to locatemobile devices that are connected to a Wi-Fi™ network, according to someembodiments. The BLE beacon sensors can be used to provide a preciselocation of people who may carry a mobile device, or may carry a beacon(e.g., a work ID, card key, etc.), according to some embodiments. Thesmart table system 100 may determine a total number of people within anarea using multiple IoT devices 190 at the same time, according to someembodiments. In various embodiments, the IoT devices 190 (also referredto herein as “input/output devices”) can be integrated in any deviceand/or system described herein (e.g., in the smart table 106, in thesmart headsets 195, and so on).

In various embodiments, the smart table system 100 includes one or moresmart headsets 195. The smart headsets 195 may be headsets of varyingsizes integrated with integrated with various input/output devices(e.g., sensors, IoT devices, cameras). Furthermore, the smart headsets195 may provide a shared multi-dimensional graphical user interface forvarious scenarios. In some embodiments, each smart headsets 195 areassociated with a smart headset identifier, such as a numeric oralphanumeric code, to identify the respective smart headset to thebranch computing system 108, the provider computing system 102, and theuser devices 104. For example, in response to walking into a lobby of abranch location for a scheduled provider session, a user device 104associated with the customer may indicate to the customer which smarttable 106 to go and which of the smart headsets 195 to wear in order toinitiate the session. While described with regards to a FI, the smartheadsets 195 may be used in other scenarios. For example, the smartheadsets 195 may be used at a car dealership or car rental company, ahotel, a booking agent, and/or a medical office. The features of thesmart headsets 195 are described in greater detail below, with referenceto FIG. 2B.

FIG. 1B illustrates a depiction of a computing system 160 that can beused, for example, to implement a smart table system 100, providercomputing system 102, user device 104, smart tables 106, branchcomputing system 108, and/or various other example systems described inthe present disclosure. The computing system 160 includes a bus 162 orother communication component for communicating information and aprocessor 164 coupled to the bus 162 for processing information. Thecomputing system 160 also includes main memory 166, such as arandom-access memory (RAM) or other dynamic storage device, coupled tothe bus 162 for storing information, and instructions to be executed bythe processor 164. Main memory 166 can also be used for storing positioninformation, temporary variables, or other intermediate informationduring execution of instructions by the processor 164. The computingsystem 160 may further include a read only memory (ROM) 168 or otherstatic storage device coupled to the bus 162 for storing staticinformation and instructions for the processor 164. A storage device170, such as a solid-state device, magnetic disk or optical disk, iscoupled to the bus 162 for persistently storing information andinstructions.

The computing system 160 may be coupled via the bus 162 to a display174, such as a liquid crystal display, or active matrix display, fordisplaying information to a user. An input device 172, such as akeyboard including alphanumeric and other keys, may be coupled to thebus 162 for communicating information, and command selections to theprocessor 164. In another arrangement, the input device 172 has a touchscreen display 174. The input device 172 can include any type ofbiometric sensor, a cursor control, such as a mouse, a trackball, orcursor direction keys, for communicating direction information andcommand selections to the processor 164 and for controlling cursormovement on the display 174.

In some arrangements, the computing system 160 may include acommunications adapter 176, such as a networking adapter. Communicationsadapter 176 may be coupled to bus 162 and may be configured to enablecommunications with a computing or communications network 154 and/orother computing systems. In various illustrative arrangements, any typeof networking configuration may be achieved using communications adapter176, such as wired (e.g., via Ethernet), wireless (e.g., via WiFi™,Bluetooth™, and so on), satellite (e.g., via GPS) pre-configured,ad-hoc, LAN, WAN, and so on.

According to various arrangements, the processes that effectuateillustrative arrangements that are described herein can be achieved bythe computing system 160 in response to the processor 164 executing anarrangement of instructions contained in main memory 166. Suchinstructions can be read into main memory 166 from anothercomputer-readable medium, such as the storage device 170. Execution ofthe arrangement of instructions contained in main memory 166 causes thecomputing system 160 to perform the illustrative processes describedherein. One or more processors in a multi-processing arrangement mayalso be employed to execute the instructions contained in main memory166. In alternative arrangements, hard-wired circuitry may be used inplace of or in combination with software instructions to implementillustrative arrangements. Thus, arrangements are not limited to anyspecific combination of hardware circuitry and software.

Although an example processing system has been described in FIG. 1B,arrangements of the subject matter and the functional operationsdisclosed herein can be carried out using other types of digitalelectronic circuitry, or in computer software (e.g., application,blockchain, distributed ledger technology) embodied on a tangiblemedium, firmware, or hardware, including the structures disclosed inthis application and their structural equivalents, or in combinations ofone or more of them. Arrangements of the subject matter disclosed hereincan be implemented as one or more computer programs, e.g., one or moresubsystems of computer program instructions, encoded on one or morecomputer storage medium for execution by, or to control the operationof, a data processing apparatus. Alternatively, or in addition, theprogram instructions can be encoded on an artificially generatedpropagated signal, e.g., a machine generated electrical, optical, orelectromagnetic signal, that is generated to encode information fortransmission to suitable receiver apparatus for execution by a dataprocessing apparatus. A computer storage medium can be, or be includedin, a computer-readable storage device, a computer-readable storagesubstrate, a random or serial access memory array or device, or acombination of one or more of them. Moreover, while a computer storagemedium is not a propagated signal, a computer storage medium can be asource or destination of computer program instructions encoded in anartificially generated propagated signal. The computer storage mediumcan also be, or be included in, one or more separate components or media(e.g., multiple CDs, disks, or other storage devices). Accordingly, thecomputer storage medium is both tangible and non-transitory.

Although shown in the arrangements of FIG. 1B as singular, stand-alonedevices, one of ordinary skill in the art will appreciate that, in somearrangements, the computing system 160 may comprise virtualized systemsand/or system resources. For example, in some arrangements, thecomputing system 160 may be a virtual switch, virtual router, virtualhost, virtual server, etc. In various arrangements, computing system 160may share physical storage, hardware, and other resources with othervirtual machines. In some arrangements, virtual resources of the network154 (e.g., network 154 of FIG. 1A) may include cloud computing resourcessuch that a virtual resource may rely on distributed processing acrossmore than one physical processor, distributed memory, etc.

As used herein, the term “resource” refers to a physical or virtualized(for example, in cloud computing environments) computing resource neededto execute computer-based operations. Examples of computing resourcesinclude computing equipment or device (server, router, switch, etc.),storage, memory, executable (application, service, and the like), datafile or data set (whether permanently stored or cached), and/or acombination thereof (for example, a set of computer-executableinstructions stored in memory and executed by a processor,computer-readable media having data stored thereon, etc.).

Referring now to FIG. 2A, a block diagram of the smart tables 106 isshown, according to some embodiments. The smart tables 106 eachsimilarly include a network interface 202, a processing circuit 204, andan input/output device 220. The network interface 202, the processingcircuit 204, and the input/output device 220 may function substantiallysimilar to and include the same or similar components as the networkinterface 110, the processing circuit 112, and the input/output device122 described above, with reference to the provider computing system102. Thus, it should be understood that the description of the networkinterface 110, the processing circuit 112, and the input/output device122 of the provider computing system 102 provided above may be similarlyapplied to the network interface 202, the processing circuit 204, andthe input/output device 220 of each of the smart tables 106.

For example, the network interface 202 is similarly structured and usedto establish connections with other computing systems (e.g., theprovider computing system 102, the branch computing system 108, the userdevices 104, the smart headsets 195) via the network 154. The networkinterface 202 may further include any and/or all of the componentsdiscussed above, with reference to the network interface 110.

The processing circuit 204 similarly includes a processor 206 and amemory 208. The processor 206 and the memory 208 are substantiallysimilar to the processor 114 and the memory 116 described above. Assuch, the smart tables 106 are similarly configured to run a variety ofapplication programs and store associated data in a database (e.g.,smart table database 209) of the memory 208. For example, the smarttables 106 may be configured to run the smart table client application218 that is stored in the smart table database 209. In another example,the smart tables 106 may be configured to store various provider anduser data, such as, but not limited to, personal information (e.g.,names, addresses, phone numbers, contacts, call logs, installedapplications, and so on), authentication information (e.g.,username/password combinations, device authentication tokens (e.g.,pseudo-random code), security question answers, unique clientidentifiers, biometric data (such as digital representations ofbiometrics), geographic data, social media data, application specificdata, and so on), and provider information (e.g., token information,account numbers, account balances, available credit, credit history,exchange histories, and so on) relating to the various users and/orvarious accounts.

The smart table client application 218 may be substantially similar tothe provider client application 120 and the branch client application150, but may instead be specifically for personalized provider sessionsbetween customers and employees at the provider. For example, the smarttable client application 218 is similarly structured to provide displaysto each customer user device 104 to facilitate improved interactionsbetween customers and specific branch employees associated with eachsmart table 106. Particularly, smart table client application 218 isconfigured to communicate with the provider computing system 102, thebranch computing system 108, the user devices 104, and the smartheadsets 195, to receive instructions and notifications from theprovider computing system 102 and/or the branch computing system 104 forthe branch employees associated with each smart table 106 to performvarious tasks associated with a provider session. Accordingly, the smarttables 106 are communicably coupled to the provider computing system 102(e.g., through interactions with the provider client application 120),the branch computing system 108 (e.g., through interactions with thebranch client application 150), the user devices 104 (e.g., throughinteractions with the user client application 132), via a network (e.g.,network 154), and the smart headsets 195 (e.g., through interactionswith the smart headset client application 238), via a network (e.g.,network 154).

The smart table client application 218 may therefore communicate withthe provider computing system 102, the branch computing system 108, theuser devices 104, and the smart headsets 195, to perform severalfunctions. For example, the smart table client application 218 isconfigured to receive data from the provider computing system 102 and/orthe branch computing system 104 pertaining to necessary inputs forauthenticating a particular transaction during a provider session. Thesmart table client application 218 is further configured to allow forcommunication with the provider client application 120 to allow thevarious branch employees that operate the smart tables 106 to providequestions or comments regarding any concerns with the smart tables. Assuch, the smart table client application 218 allows for the branchemployees associated with the smart tables 106 to communicate with thecustomer, branch manager, and/or provider employees throughout theprocess of a provider session.

The input/output device 220 of each smart table 106 may functionsubstantially similar to and include the same or similar components asthe input/output device 134 described above, with reference to the userdevices 104. Accordingly, it should be understood that the descriptionof the input/output device 134 provided above may also be applied to theinput/output device 220 of each of the smart tables 106. For example,the input/output device 220 of each smart table 106 is similarlystructured to receive communications from and provide communications tocustomers paired (e.g., via a network connection, communicably coupled,via Bluetooth™, via a shared connection, and so on) with a smart table106 and to the branch employee or branch employees associated with eachsmart table 106.

The processing circuit 204 also includes a provider session managementcircuit 210, a viewport monitoring circuit 252, an authenticationcircuit 212, a notification generation circuit 214, and a cash dispensermanagement circuit 216, for example. In other embodiments, theprocessing circuit 204 may contain more or less components than shown inFIG. 2A. The components of FIG. 2A are meant for illustrative purposesonly, and should not be regarded as limiting in any manner. The providersession management circuit 210 may be configured to detect a triggerevent for a provider session with the smart table 106. A providersession may include one customer (e.g., the smart table 106 isconfigured as a self-service ATM), a branch employee and a customer, abranch employee and more than one customer, and/or more than one branchemployee and a customer, and/or more than one branch employee and morethan one customer, according to some embodiments. For example, twocustomers that have a joint account together may participate in aprovider session with a branch employee. In some embodiments, a triggerevent includes detecting a user device 104 within a communication rangeof the smart table 106. In other embodiments, a trigger event includesthe activation of a selectable icon on a graphical user interface of thesmart table 106. In response to detecting a trigger event, the providersession management circuit 210 may be configured to send instructions tothe notification generation circuit 214 to request input for customerand/or employee authentication.

In some embodiments, the provider session management circuit 210 isfurther configured to receive sensor data from the input/output device220 of the smart table 106. For example, the provider session managementcircuit 210 may be configured to receive camera data of documents that acustomer wants to scan and save, movement data from a motion detector,temperature sensor data, audio data indicating a selection and/oraction, haptic feedback indicating selection action, and so on.Additionally, the provider session management circuit 210 may determinewhen to send reminders to a user device 104 and/or smart headset 195 ofthe branch employee regarding a provider session (e.g., to fill out acertain form, an individual's stress level, elevated access, managerhelp, to pre-load a compartment of the smart table 106) and/or when tosend a session end reminder for a scheduled provider session. Forexample, the provider session management circuit 210 may be configuredto track how much time is remaining in a scheduled session to wrap up aprovider interaction with the customer.

In some embodiments, the provider session management circuit 210 canfurther be configured to generate content for display to users (e.g.,employees, users, managers, and so on). The content can be selected fromamong various resources (e.g., webpages, applications, databases, and soon). The provider session management circuit 210 is also structured toprovide content (e.g., graphical user interface (GUI)) to the smarttables 106 and smart headsets 195, over the network 154, for displaywithin the resources. For example, in various arrangement, a customizeddashboard may be integrated in an institution's application (e.g.,provider client application 120, branch client application 150, userclient application 132, and smart table client application 218 of FIG. 2) or provided via an internet browser. In various embodiments, thecontent from which the provider session management circuit 210 selectsmay be provided by the provider computing system 102 and/or branchcomputing system 108 (e.g., via the network 154) to one or more smarttables 106 and/or smart headsets 195. In some implementations, providersession management circuit 210 may select content to be displayed on theuser devices 104. In various implementations, the provider sessionmanagement circuit 210 may determine content to be generated andpublished in one or more content interfaces of resources (e.g.,webpages, applications, and so on).

In various embodiments, the provider session management circuit caninclude a viewport monitoring circuit 252. The viewport monitoringcircuit 252 can be configured to cause the smart table 106 to identify aplurality of coordinate values of the graphical user interface based onrelative position of content items in a resource (sometimes referred toherein as a “viewport”) of the smart table 106. For instance, as shownin FIGS. 4-9 , a viewport can be a touchscreen display configured toreceive information from the smart table 106 indicative of a selection(e.g., touchscreen selection) of a document associated with the viewportor a content item. In some implementations, the viewport monitoringcircuit 252 can be configured to monitor a position of the scroll tabrelative to the scroll bar or relative to the viewport based on, forinstance, scroll information received from the smart table 106. That is,state information relating to the position of the content item within anapplication (e.g., smart table client application 218) is acquired andused in the subsequent determining of the values of the one or moreproperties of the viewport.

The viewport monitoring circuit 252 can be configured to cause the smarttable 106 to monitor a viewport of an application to append (e.g.,modify the values for the one or more properties) one or more of thecontent items identified by the smart table client application 218. Insome implementations, the content item can be a document object modelelement (i.e., DOM). In some implementations, the content item can be aDOM element that can be rendered for presentation on the touchscreendisplay of the smart table 106. In some implementations, the contentitem can be a visual representation of a DOM element that can berendered for presentation on the touchscreen display of the smart table106. In some implementations, the content item can be an image, a video,a document, an animation, among others.

In some implementations, the viewport monitoring circuit 252 can beconfigured to cause the smart table 106 to determine coordinates of thecontent items relative to a reference point of the smart table clientapplication 218. In some implementations, the reference point of thesmart table client application 218 can include a top corner of theapplication. In some implementations, the viewport monitoring circuit252 can determine that the application is configured to extendvertically or horizontally. In implementations in which the applicationis configured to extend vertically, the viewport monitoring circuit 252can cause the smart table 106 to determine a coordinate value of contentitems along the vertical axis, or stated differently, the y-axiscoordinate. In implementations in which the application is configured toextend horizontally, the viewport monitoring circuit 252 can cause thesmart table 106 to determine a coordinate value of content items alongthe horizontal axis, or stated differently, the x-axis coordinate. Thecoordinate value can be a number of pixels, a distance, or a scaleddistance from the reference point of the application. In someimplementations, the coordinate value can be a percentage correspondingto a point of the content items, for instance, a top edge of the contentitems.

In some implementations, the viewport monitoring circuit 252 can beconfigured to cause the touchscreen display of the smart table 106 todetect if a user activity occurred within and/or in the environment ofthe touchscreen display (e.g., from an input/output device 220) and/orsmart table 106. For instance, the viewport monitoring circuit 252 canbe configured to receive information from the application indicative ofa movement (e.g., up or down) of a scroll tab of a scroll bar associatedwith the viewport or the application. In some implementations, theviewport monitoring circuit 252 can determine if scroll activityoccurred by employing one or more listeners that detect scroll activity.In another instance, the viewport monitoring circuit 252 can beconfigured to receive sensor input from one or more input/output device220 (and/or from IoT devices 190) around the environment (e.g., at thesmart table 106, within the space, within the building, and so on). Inone example, the sensor input may be a hand gesture (e.g., wave, swipe,point) of an individual that does not contact the touchscreen display.In one example, the sensor input may be an audible and/or visual outputof an individual indicating a specific action to be performed (e.g.,selection action, fill-in action, type action, next page action, headaction, foot action, and so on) from one or more input/output device 220(and/or from IoT devices 190) around the environment.

The authentication circuit 212 may be configured to determine whether auser is authenticated to initiate a provider session and/or to completecertain provider tasks. For example, the authentication circuit 212 maybe configured to request an authorization approval from the providercomputing system 102 of a received PIN or biometric input. In someembodiments, the authentication circuit 212 is also configured todetermine the level of authentication necessary to complete differenttypes of financial tasks (e.g., withdrawal cash, take out a loan, make anew investment, change address, request new debit card, etc.). Theauthentication circuit 212 may be configured to generate a score of howauthenticated a user is during a provider session. For example, a userthat entered both a biometric input and an alphanumeric passcode mayreceive a first score of 100% authenticated, and a user that onlyentered a PIN may receive a second score of 50% authenticated. Theauthentication circuit 212 is also configured to send instructions tothe cash dispenser management circuit 216 in response to receiving anapproved authorization (e.g., from the provider computing system via thenetwork 154) to dispense cash to a customer for a withdrawal request.

The notification generation circuit 214 may be configured to createalerts regarding an upcoming provider session, an in-progress providersession, and/or a completed provider session, according to someembodiments. The notification generation circuit 214 may also receiveinstructions on the format of a notification from the provider sessionmanagement circuit 210. In some embodiments, the notification generationcircuit 214 is configured to instruct the input/output device 220 of thesmart table 106 to provide audible and/or visual output to a customerregarding information displayed during a provider session. For example,the notification generation circuit 214 may be configured to cause anNFC icon on a graphical user interface of the smart table 106 to flashto indicate to a user to place a user device 104 on the NFC icon to pairto the smart table 106. As another example, the notification generationcircuit 214 may be configured to generate a notification that outputs avoice-over indicating the provider session will terminate within acertain time interval, such as a five minute warning to complete anyunfinished tasks.

Still referring to FIG. 2A, the cash dispenser management circuit 216may be configured to control the use of the cash dispenser of the smarttable 106. In some embodiments, the cash dispenser management circuit216 is further configured to determine when the amount of available cashat the smart table 106 is below a threshold value (e.g., $100). The cashdispenser management circuit 216 may then instruct the notificationgeneration circuit 214 to create a notification of the low amount ofcash at the smart table 106 to the branch computing system 108 and/or auser device 104 (e.g., a branch manager user device 104). In someembodiments, the cash dispenser management circuit 216 is alsoconfigured to transmit an instruction to update a balance of thecustomer account to the provider computing system 102, for example,after the transaction request is completed. The cash dispensermanagement circuit 216 may further be configured to instruct theinput/output device 220 of the smart table 106 to print a receipt withtransaction details, such as the amount of cash withdrawn, the time ofthe completed transaction, and/or an updated balance for the customeraccount used to complete the transaction.

The card printing circuit 217 may be configured to control the use ofthe card printer of the smart table 106. In some embodiments, the cardprinting circuit 217 is further configured to determine variousinformation for printing a card (e.g., debit card, credit card, rewardscard, and so on). For example, a pseudo-random number (e.g., debit cardnumber unique to an individual and/or a particular account of theindividual) for the card may be generated by the card printing circuit217. In another example, a design (e.g., color, artwork, templates) forthe card may be determined based on a user preference and/or smart table106 preference. In some embodiments, the card printing circuit 217 isalso configured to transmit an instruction to update a card of thecustomer account to the provider computing system 102, for example,after a new card is printed. The card printing circuit 217 may furtherbe configured to instruct the input/output device 220 of the smart table106 to print a receipt with card details, such as the limit on the card,the name on the card, an updated card verification value (CVV), anupdated PIN, and so on.

The use of the smart table 106 within the smart table system 100 maybeneficially reduce significant amounts of time to complete providerinteractions during a provider session and/or fill out paperwork forms.Furthermore, the smart tables 106 may help improve transparency ofcustomer account information and employee services and increaseface-to-face time with the branch employees. By providing a largergraphical user interface to share customer account information, ratherthan on a tiny screen on a single user device, the smart tables 106 alsoincrease the amount of inclusion for each party participating in theprovider session. The smart tables 106 may additionally help informcustomers of several choices and advise the customers by displayinginformation from the branch employee regarding the customer accountinformation utilizing visual tools. In some embodiments, the visualtools may include pie charts, bar graphs, scatterplots, user graphics,and so on. The smart tables 106 may be configured such that a customersits while using, or may be configured such that a customer stands whileusing.

Referring now to FIG. 2B, a block diagram of the smart headsets 195 isshown, according to some embodiments. The smart headsets 195 eachsimilarly include a network interface 222, a processing circuit 224, andan input/output device 240. The network interface 222, the processingcircuit 224, and the input/output device 240 may function substantiallysimilar to and include the same or similar components as the networkinterface 110, the processing circuit 112, and the input/output device122 described above, with reference to the provider computing system102. Thus, it should be understood that the description of the networkinterface 110, the processing circuit 112, and the input/output device122 of the provider computing system 102 provided above may be similarlyapplied to the network interface 222, the processing circuit 224, andthe input/output device 240 of each of the smart headsets 195.

For example, the network interface 222 is similarly structured and usedto establish connections with other computing systems (e.g., theprovider computing system 102, the branch computing system 108, the userdevices 104, the smart tables 106) via the network 154. The networkinterface 222 may further include any and/or all of the componentsdiscussed above, with reference to the network interface 110.

The processing circuit 204 similarly includes a processor 226 and amemory 228. The processor 226 and the memory 228 are substantiallysimilar to the processor 114 and the memory 116 described above. Assuch, the smart headsets 195 are similarly configured to run a varietyof application programs and store associated data in a database (e.g.,smart headset database 229) of the memory 228. For example, the smartheadsets 195 may be configured to run the smart headset clientapplication 238 that is stored in the smart headset database 229. Inanother example, the smart headsets 195 may be configured to storevarious provider and user data, such as, but not limited to, personalinformation (e.g., names, addresses, phone numbers, contacts, call logs,installed applications, and so on), authentication information (e.g.,username/password combinations, device authentication tokens, securityquestion answers, unique client identifiers, biometric data (such asdigital representations of biometrics), geographic data, social mediadata, application specific data, and so on), and provider information(e.g., token information, account numbers, account balances, availablecredit, credit history, exchange histories, and so on) relating to thevarious users and/or various accounts.

The smart headset client application 238 may be substantially similar tothe provider client application 120, the branch client application 150,and the smart table client application 218, but may instead bespecifically for personalized provider session views between varioususers (e.g., customers, employees, and managers at the provider). Forexample, the smart headset client application 238 is similarlystructured to provide personalized views to each smart headset 195 tofacilitate improved content presentation to various users of a session(e.g., customer, employee, manager, and so on) associated with eachsmart table 106 and one or more smart headsets 195. Particularly, smartheadset client application 238 is configured to communicate with theprovider computing system 102, the branch computing system 108, the userdevices 104, and the smart tables 106 to receive instructions andnotifications from the provider computing system 102, and/or the branchcomputing system 104, for the branch employees and/or manager associatedwith each smart headset 195 to perform various tasks associated with aprovider session. Accordingly, the smart headsets 195 are communicablycoupled to the provider computing system 102 (e.g., through interactionswith the provider client application 120), the branch computing system108 (e.g., through interactions with the branch client application 150),the user devices 104 (e.g., through interactions with the user clientapplication 132), and the smart tables 106 (e.g., through interactionswith the smart table client application 218), via a network (e.g.,network 154).

The smart headset client application 238 may therefore communicate withthe provider computing system 102, the branch computing system 108, theuser devices 104, and the smart tables 106, to perform severalfunctions. For example, the smart headset client application 238 isconfigured to receive data from the provider computing system 102 and/orthe branch computing system 104 pertaining to necessary inputs forauthenticating a particular transaction during a provider session. Inthis example, the smart headset client application 238 may magnify,highlight, color, bold, and/or variously emphasize necessary input. Inanother example, the smart headset client application 238 is configuredto receive data from the smart table 106 and overlay additional contentand/or provide additional input (e.g., audio, vibrations, light, colors,and so on) on (e.g., display) and/or in (e.g., sensors) the smartheadsets 195 pertaining to the content displayed on the smart table 106.In this example, the smart headset client application 238 may providenotifications, tools (e.g., settings icons, menu options, customizationoptions, and so on), status indicators (e.g., session completionpercentage, emotional state, task in progress), and various sensor input(e.g., from IoT devices 190). The smart headset client application 238is further configured to allow for communication with the providerclient application 120 to allow the various branch employees thatoperate the smart headsets 195 to provide questions or commentsregarding any concerns with the smart tables. As such, the smart headsetclient application 238 allows for the branch employees associated withthe smart headsets 195 to communicate with the customer, branch manager,and/or provider employees throughout the process of a provider session.

The input/output device 240 of each smart headset 195 may functionsubstantially similar to and include the same or similar components asthe input/output device 134 described above, with reference to the userdevices 104. Accordingly, it should be understood that the descriptionof the input/output device 134 provided above may also be applied to theinput/output device 240 of each of the smart headsets 195. For example,the input/output device 240 of each smart headset 195 is similarlystructured to receive communications from and provide communications tocustomers paired (e.g., via a network connection, communicably coupled,via Bluetooth™, via a shared connection, and so on) with a smart headset195 and to the branch employee or branch employees associated with eachsmart headset 195. In various implementations, the input/output device240 can include various cameras and/or sensors within the housing of thesmart headset 195. For example, the smart headset 195 can include one ormore cameras (e.g., for detecting movement, motion, and viewenvironment), audio sensor, temperature sensor, haptic feedback sensor,biometric sensor, pulse oximetry (detect oxygen saturation of blood),altitude sensor, humidity sensor, magnetometer, accelerometer,gyroscope, stress sensors, various IoT devices 190, and so on.

The processing circuit 204 also includes a provider session managementcircuit 230, an authentication circuit 232, a notification generationcircuit 234, and a viewport monitoring circuit 254, for example. Inother embodiments, the processing circuit 224 may contain more or lesscomponents than shown in FIG. 2B. The components of FIG. 2B are meantfor illustrative purposes only, and should not be regarded as limitingin any manner. The provider session management circuit 230 and viewportmonitoring circuit 254 of each smart headset 195 may functionsubstantially similar to and include the same or similar components asthe provider session management circuit 210 and viewport monitoringcircuit 252 respectively. Accordingly, it should be understood that thedescription of the provider session management circuit 210 and viewportmonitoring circuit 252 provided above may also be applied to theprovider session management circuit 230 and viewport monitoring circuit254 of each of the smart headsets 195. For example, the provider sessionmanagement circuit 230 of each smart headset 195 is similarly structuredto be configured to detect trigger events for provider sessions andmonitor a viewport (e.g., by the and viewport monitoring circuit 254) ofthe smart headsets 195 (explained in detail with reference to FIGS.13-17 ).

The authentication circuit 232 of each smart headset 195 may functionsubstantially similar to and include the same or similar components asthe authentication circuit 212. Accordingly, it should be understoodthat the description of the authentication circuit 212 provided abovemay also be applied to the authentication circuit 232 of each of thesmart headsets 195. For example, the authentication circuit 232 of eachsmart headset 195 is similarly structured to determine whether a user isauthenticated to initiate a provider session and/or and a level ofauthentication necessary to complete different types of financial tasks.

The notification generation circuit 234 of each smart headset 195 mayfunction substantially similar to and include the same or similarcomponents as the notification generation circuit 214. Accordingly, itshould be understood that the description of the notification generationcircuit 214 provided above may also be applied to notificationgeneration circuit 234 of each of the smart headsets 195. For example,the notification generation circuit 234 of each smart headset 195 issimilarly structured to create and provide alerts regarding an upcomingprovider session, an in-progress provider session, and/or a completedprovider session.

Referring now to FIG. 3 , a flow diagram of a method 300 for initiatinga session between one or more user devices 104 and a smart table 106 isshown, according to some embodiments. The method 300 may be provided byand/or accessible by the provider client application 120, the branchclient application 150, the user client application 132, and the smarttable client application 218, for example. The method 300 may beperformed by the smart table system 100 described above pertaining toFIGS. 1 and 2 . In some embodiments, the method 300 begins in responseto receiving, by a smart table 106, a session trigger event. A sessiontrigger event may be any event that triggers the beginning of a sessionbetween the smart table 106 and a user device 104. For example, when acustomer is within a certain proximity of the smart table 106, the userdevice 104 associated with the customer that the customer is holding maybe within a wireless communication range of various devices (e.g., thebranch computing system 108 and/or the smart table 106) associated withthe branch location. In response to entering the wireless communicationrange, the respective user device 104 may be configured to automaticallyrequest the customer, via the user device 104, to enter confirmation toestablish a secure connection with the smart table 106. As such, thesecurity of the provider session may increase, as a customer may berequired to be within a certain proximity (e.g., latitude and longitude)of the smart table 106 to begin the provider session. In someembodiments, similarly, a user device 104 of an employee scheduled to berunning a provider session for the smart table 106 may also be requiredto be within proximity of the smart table 106 in order to initiate theprovider session. A session trigger event may also include receiving aninput via input/output device 220, such as receiving a user interactionvia a touch screen display of the smart table 106. In other embodiments,a session trigger event may include a customer or employee logging intoa user client application 132 on a user device 104. In additionalembodiments, a session trigger event may occur at a specific time, suchas in response to the provider session management circuit determiningthere is a scheduled provider session at a smart table 106 at a specifictime. In some embodiments, the smart table 106 may be configured tooperate in a low power mode or “sleep mode” until a session triggerevent is received.

At 302, the method 300 includes generating and transmitting anotification to a customer device (e.g., a user device 104) to providean input for authentication. In some embodiments, the notificationgeneration circuit 214 is configured to execute step 302 in response toreceiving an instruction from the provider session management circuit210. The notification generation circuit 214 may be configured togenerate a notification requesting user authentication based oninformation received, via the network 154, from the smart tablemanagement circuit 148 and customer account database 118. For example,specific smart tables 106 may require higher levels of authenticationbefore a user may initiate a provider session based on the capabilitiesof the smart table. Additionally, the customer account database 118 mayhave stored customer preferences indicating one or more types of inputthe customer wants to use for authenticating a provider session. Inputfor authentication may include a personal identification number (PIN), abiometric input (e.g., a fingerprint, a palm print, an eye scan, a voicesample, etc.), a haptic device input (e.g., rings, jewelry, headsets,bands), smart headsets input, an alphanumeric passcode, a barcode, a QRcode, a physical key, an electronic key (e.g., a token stored on theuser device 104 of the customer), a physical or mobile wallet card(e.g., a credit card with chip technology, a virtual provider card), andso on. In some embodiments, the generated notification may includeaudible or tactile output when received by the user device 104. Forexample, in response to receiving the generated notification, the userdevice 104 may create an audible sound, via the input/output device 134,to catch the attention of the customer and/or an employee working withthe customer and/or may cause the user device 104 to vibrate.

In other embodiments, instead of transmitting the notification to a userdevice 104, the notification requesting an input to authenticate thecustomer is shown on a display screen of the smart table 106. Forexample, the notification generation circuit 214 may generate anotification requesting a customer to place a palm on a highlighted areaof the display screen of the smart table 106. As another example, thenotification generation circuit 214 may provide a notification shown onthe display screen of the smart table 106 asking a customer to enter acustomer PIN on the customer's user device 104. In some embodiments, thegenerated notification also includes a message to place the user device104 associated with the customer on a particular area of the smart table106. For example, a highlighted area may indicate where to place theuser device 104 in order to facilitate using near-field communicationdata exchange.

The input to authenticate initiation of a provider session is receivedat step 304. In some embodiments, the authentication circuit 212 isconfigured to receive the input to authorize initiating the providersession. One or more inputs may be received at step 304, according tosome embodiments. For example, in some provider sessions, more than onecustomer may be detected and/or scheduled to participate in the providersession. As such, the authentication circuit 212 may receive inputs fromeach customer for the provider session. Additionally, an input toauthenticate an employee scheduled to participate in the providersession may also be received at 304. For example, for provider sessionsscheduled to conduct transactions with higher security, a branch managermay be required in order to initiate the provider session. As such,authentication inputs may be received from the customer and the branchmanager at step 304.

In some embodiments, the inputs are received via the user devices 104and transmitted to the smart table 106 via the network 154. In otherembodiments, the one or more inputs may be received directly by thesmart table 106 via the input/output device 220. For example, a PIN forauthentication may be entered via a user interface of the customer'suser device 104, or a fingerprint may be entered via the input/outputdevice 220 (e.g., a fingerprint scanner) of the smart table 106.Beneficially, a customer may then enter personal authenticationinformation in a more private setting, rather than entering personalauthentication information on the smart table 106. As such, the securityof the customer's personal information may be improved.

At step 306, the method 300 includes determining whether one or moreusers are authenticated to initiate the provider session. In someembodiments, the authentication circuit 212 is configured to determinewhether authentication for the provider session is successful. Thenetwork interface 202 may transmit, via the network 154, the receivedinput to the branch computing system 108 and/or the provider computingsystem 102. In some embodiments, the provider computing system 102and/or the branch computing system 108 then determine whether thereceived input matches user information stored in a database (e.g., incustomer account database 118, in employee database 144). For example,the provider computing system 102 determines whether a device tokenreceived from the user device 104 matches a token stored in a tokenvault of the customer account database 118. The network interface 202may then receive confirmation or a denial of authentication for the oneor more users (e.g., a customer, a customer and an employee, more thanone customer, etc.). In some embodiments, the authentication circuit 212is configured to execute step 306 at certain intervals throughout aprovider session. For example, after a predetermined time interval, orat the end of a scheduled provider session, the authentication circuit212 may be configured to re-authenticate the one or more customersand/or employee.

In response to determining one or more of the users were notauthenticated, the method 300 proceeds to step 308. The method 300includes generating and transmitting a notification for an unauthorizedaccess attempt at step 308. In some embodiments, the notificationgeneration circuit 214 is configured to execute the operations at 308.The notification generation circuit 214 may be configured to generate atext notification, an email notification, an automated voiceovernotification, and/or any kind of alert to notify a user. Thenotification generation circuit 214 may be configured to include detailsconcerning the access attempt in the generated notification. Forexample, the notification may include branch location information (e.g.,name, address) and/or a timestamp of when the attempt to initiate aprovider session was denied. In some embodiments, the notification alsomay include contact information for a branch manager and instructionsconcerning the security of a customer's personal data. For example, thegenerated notification may include options to view user account details,transaction history, previous provider session history, and so on. Thegenerated notification may also include selectable options to change oneor more inputs for authentication (e.g., change a user passcode, changea user PIN, print a new card, etc.) and/or user preferences (e.g.,preferences for increased security before access is granted to customerinformation). In some embodiments, the notification is transmitted to auser device 104 associated with a customer. The notification may also betransmitted, via the network 154, to a user device 104 associated with abranch manager and/or an employee assigned to a scheduled providersession.

On the other hand, if the authentication circuit 212 determines at step306 that the one or more users are successfully authenticated, themethod 300 proceeds to step 310. At step 310, the method 300 includesgenerating and providing a notification of a successful pairing betweencustomer device (e.g., user device 104) and the smart table 106 for theprovider session. In some embodiments, the notification generationcircuit 214 is configured to generate a text alert or email alertindicating the establishment of a secure communication session with thesmart table 106. The type of generated notification (e.g., email, text,phone call, etc.) may be based on user preferences. For example, theprovider session management circuit 210 may receive session preferencesfor a customer stored in customer account database 118. The providersession preferences may include the kind of notifications the customerwants to receive. The preferences may also include information on whereto direct the generated notification. For example, customer preferencesmay include contact information (e.g., an email of a parent of thecustomer, a phone number, etc.) to send the generated notification. Assuch, in some embodiments, the notification may be provided to one ormore user devices 104. The generated notification for a successfulpairing between the customer user device 104 and the smart table 106 mayalso be provided via the input/output device 220 of the smart table 106.For example, the smart table 106 may show the notification on a displayscreen.

At step 312, the method 300 includes retrieving customer accountinformation for the customer account associated with the pair customeruser device 104. In some embodiments, the provider session managementcircuit 210 is configured to execute step 312. The provider sessionmanagement circuit 210 may be configured to request, via the networkinterface 202, customer account information from the provider computingsystem 102. In some embodiments, the amount of customer accountinformation retrieved is relative to the security of the providersession. For example, the customer account information retrieved isrelative to the type of input received for user authentication. As anexample, if only a passcode was entered, the customer accountinformation that is retrieved may be more limited than if a passcode anda biometric input were entered to authenticate the customer. In someembodiments, customer account information may include previous providersession history, transaction history for the customer account, balancesfor various accounts (e.g., savings accounts, checking accounts, creditcard accounts), loan information, mortgage information, personalinformation (e.g., name, address, age, education, occupation, salary,etc.), credit card debt, current investments, retirement plans, savingsgoals, and so on. The provider session management circuit 210 may alsobe configured to pull specific documents concerning planned transactionsfor a scheduled provider session at 312. For example, a prepareddocument regarding a loan may be retrieved at step 312 for a branchemployee to review with the customer during the scheduled providersession.

Once the customer account information has been retrieved, at step 314,the customer account information may be displayed on the smart table 106for the authenticated provider session. In some embodiments, thecustomer account information may be displayed in a customer area of adisplay screen of the smart table 106. In other embodiments, thecustomer account information may be displayed on the customer's userdevice 104 rather than on a display screen of the smart table 106. Forexample, for certain customer account information that is moreconfidential, such as a social security number, and/or customer accountinformation that a customer indicated in preferences should not be shownduring a provider session on a smart table, such as a salary or thecustomer's overall financial worth, the provider session managementcircuit 210 may be configured to only provide that information on thecustomer's user device 104. In some embodiments, the customer accountinformation may be displayed using tables, graphics, and/or other visualtools to help convey the data to the customer in a meaningful manner.For example, concerning retirement, a graphic may show a portion of thecustomer's current earnings that should be set aside for retirement andthe progress the customer has made in saving for retirement over aspecific period of time.

Referring now to FIG. 4 , an illustration of various configurations ofthe smart table 106 are shown, according to some embodiments. Aperspective view 402 of a smart table 106 depicts a storage compartmentbeneath a top surface of the smart table 106. In some embodiments, thecash dispenser of the smart table 106 may be accessed by lifting a topsurface of the smart table 106. As such, the cash dispenser and/orvarious input/output devices (collectively referred to herein as “IoTdevices 410”) may easily be serviced by lifting the top surface of thesmart table 106, covering the storage compartment. In other embodiments,a storage compartment of the smart table 106 may be accessed by slidingthe top surface (e.g., perspective view 408) to a side of the smarttable 106, rather than lifting the top surface. A perspective view 404of a smart table 106 shows an integration of storage compartments forthe smart table 106 and a digitally enabled, touch screen display,according to some embodiments. A perspective view 406 of a smart table106 depicts a touch screen display encompassing the top surface of thesmart table 106. In some embodiments, the smart table 106 may notinclude a cash dispenser, as shown in perspective view 406. The viewsshown in FIG. 4 are meant to be illustrative in purpose only, and shouldnot be regarded as limiting in any manner.

Referring now to FIG. 5 , an illustration of additional configurationsof the smart table is shown, according to some embodiments. Perspectiveview 502 depicts a smart table 106 with a touch screen display and legs506 at a set height. Perspective view 504 shows a smart table 106including a touch screen display and legs 508. In some embodiments, thelegs 508 may be adjusted to varying heights based on user preference.For example, a user may increase or decrease the height of the smarttable 106 by operating motorized lifting columns to increase or decreasethe height of the legs 508. In some embodiments, the motorized liftingcolumns of the legs 508 are activated using a switch on the smart table106. In other embodiments, the height of the smart table 106 isincreased or decreased by entering an input via a touch screen of thesmart table 106. A perspective view 506 of a smart table 106 depicts astorage compartment beneath a top surface of the smart table 106. Insome embodiments, the cash dispenser of the smart table 106 may beaccessed by sliding (or lifting) a top surface of the smart table 106.As such, the cash dispenser and/or various input/output devices(collectively referred to herein as “IoT devices 510”) may easily beserviced by sliding (or lifting) the top surface of the smart table 106,covering the storage compartment.

Referring now to FIG. 6 , an illustration of a user interface 600 of thesmart table 106 and paired user devices 104 is shown, according to someembodiments. The user interface 600 may be provided by the smart tableclient application 218. In some embodiments, the user interface 600 isgenerated and displayed, via an input/output device 220, by the providersession management circuit 210. The user interface 600 includes accountsummary window 604, for example. The account summary window 604 mayinclude a name, address, photo identification, and contact informationfor a customer. In some embodiments, the account summary window 604 isdisplayed in response to receiving a selection of a profile icon on theuser interface 600. The user interface 600 also includes a device area602. In some embodiments, the device area 602 includes a charging iconand a wireless connection icon. The connection icon may indicate to oneor more users (e.g., a customer, two customers, a customer and anemployee, etc.) where to place a user device 104 in order to pair to thesmart table 106. As such, the connection icons shown on the userinterface 600 may be used as indicators of the locations of NFC tagswithin the smart table 106. In some embodiments, the user interface 600may utilize different colors to indicate a successful pairing and anunsuccessful pairing in device area 602. For example, the connectionicon may turn green in response to a successful pairing to therespective user device 104 placed over the connection icon. AlthoughFIG. 6 depicts two user devices 104, the smart table 106 may beconfigured to pair to more than two different user devices 104,according to some embodiments.

Referring now to FIG. 7 , an illustration 700 of a user interface of thesmart table 106 configured to receive an input from a customer orprovider representative is shown, according to some embodiments. Theillustration 700 depicts a keyboard 702, a customer device 704, and anemployee device 706. The customer device 704 and the employee device 706may both be the same or similar as the user devices 104 described above.In some embodiments, the keyboard 702 is displayed on a user interfaceof the smart table 106 to provide an input for the customer. Thekeyboard 702 may be displayed to enter new information, such as a changeof address for the customer. In some embodiments, the keyboard 702 isoriented on a display screen of the smart table 106 based on whether acustomer or an employee needs to enter information. For example, thesmart table 106 may serve as a desk for a provider employee (e.g., alawyer, a consultant, a real estate agent). As such, while sitting downat the smart table 106, the customer and the branch employee may beseated on opposite sides of the smart table 106. In some embodiments,the input/output device 220 of the smart table 106 is configured todetermine an orientation and position for the keyboard 702 based on datareceived from sensors and/or cameras of the smart table 106.

Referring now to FIG. 8 , an illustration 800 of the smart table 106including a dispensing mechanism 802 is shown, according to someembodiments. The dispensing mechanism 802 can be a cash dispenser,though it will be appreciated that the dispensing mechanism 802 can beconfigured to dispense any type of item, such as cash, a receipt,checks, stamps, and so on. Accordingly, the smart table 106 maybeneficially be utilized as an automated teller machine (ATM). In someembodiments, the smart table 106 may be used as an assisted-service ATM,as shown in FIG. 7 . The smart table 106 may also function as a stationfor tellers at a branch location. In other embodiments, the smart table106 may be used as a self-service ATM, without using employees tosupervise the transaction at the smart table 106. The smart table 106may be configured to pair with the user device 104 of the customerbefore dispensing cash via the dispensing mechanism 802. For example,the dispenser management circuit 216 is configured to receive approvalfrom the authentication circuit 212 before providing cash to a customerusing the smart table 106.

Referring now to FIG. 9 , an illustration 902 of various user interfaceorientations displayable by the smart table 106 is shown, according tosome embodiments. A first user interface orientation 902 includes a userinterface of a smart table 106 with half of a customer interface areaand half of a branch employee interface area. In some embodiments, thebranch employee interface area is rotated 180 degrees from the customerinterface area in a traditional setting for when the branch employee ison an opposite side of the smart table 106 from the customer. A seconduser interface orientation 904 includes a user interface of the smarttable 106 with the customer interface area and the branch employeeinterface area rotated 90 degrees from the customer interface area for amore casual setting. A third user interface orientation 906 includes auser interface of the smart table 106 with one interface area for boththe customer and the branch employee. In some embodiments, the thirduser interface orientation 906 shows the customer interface area forwhen the customer and the branch employee are on the same side of thesmart table 106, for example.

Referring now to FIG. 10 , an illustration of example user interfaces ofthe user device 104 when the user device 104 is paired to the smarttable 106 is shown, according to some embodiments. FIG. 10 includes userinterface 1002 and user interface 1004. In various embodiments, the userinterface 1002 and the user interface 1004 are generated by the smarttable system 100 described above with reference to FIG. 1A. In someembodiments, the user interface 1002 and the user interface 1004 aregenerated during the method 300 described above with reference to FIG. 3. The user interface 1002 may be displayed on a user device 104associated with a customer attempting to pair to a smart table 106, forexample. The user interface 1002 may include activatable icons forselecting various options regarding authenticating the customer. In someembodiments, the user interface 1002 includes a password activatableicon 1006 and a new customer activatable icon 1008. In response toreceiving a user selection of the password activatable icon 1006, aprompt, generated by the notification generation circuit 214, to enter apassword for customer authentication may be displayed. Upon selection ofthe new customer activatable icon 1008, the notification generationcircuit 214 may generate and display a new user interface requesting theuser to fill out information to create an account (e.g., a provideraccount associated with the provider).

The user interface 1004 may be displayed on the user device 104 inresponse to successful authentication and pairing with the smart table106. In some embodiments, the user interface 1004 includes activatableicons list 1010 for selecting various options regarding accounts of thecustomer. For example, the activatable icons list 1010 may includeoptions to view information pertaining to a checking account, a savingsaccount, a debit card, a credit card, and/or foreign exchange. The userinterface 1004 may also include a cancel activatable option 1012. Insome embodiments, in response to selection of the cancel activatableoption 1012, the provider session ends and the established connectionbetween the smart table 106 and the one or more paired user devices 104ends. In some embodiments, the user device 104 may return to a home pageof the user client application 132 in response to receiving a selectionof the cancel activatable option 1012.

The terms selectable and activatable are used interchangeably herein.Selectable/activatable icons presented as part of example GUIs may causea signal to be generated upon selection/activation. The signal may betransmitted to a system, device, or application to indicate to thedevice, system, or application which icon has been selected, and thedevice, system, or application may respond accordingly.

Referring now to FIG. 11 , a flow diagram of a method 1100 for managingcontent with the smart table and smart headsets of FIG. 1A, according toexample embodiments. Provider computing system 102, user devices 104,smart tables 106, branch computing system 108, IoT devices 190, andsmart headsets 195 can be configured to perform operations of the method1100.

In broad overview of method 1100, at block 1102, one or more processingcircuits (e.g., provider computing system 102, user devices 104, smarttables 106, branch computing system 108, IoT devices 190, and smartheadsets 195 in FIG. 1A, and computing system 160 in FIG. 1B, and so on)can generate graphical user interfaces. At block 1104, the one or moreprocessing circuits (sometimes referred to herein as “a processingcircuit”) can provide the graphical user interfaces. At block 1106, theone or more processing circuits can receive sensor device dataassociated with at least one of biological data or behavioral data. Atblock 1108, the one or more processing circuits can, in response toreceiving the sensor device data, update a first graphical userinterface for a first smart headset. At block 1110, the one or moreprocessing circuits can, in response to receiving the sensor devicedata, update a second graphical user interface for a second smartheadset. Additional, fewer, or different operations may be performed inthe method depending on the particular arrangement. In somearrangements, some or all operations of method 1100 may be performed byone or more processors executing on one or more computing devices,systems, or servers. In various arrangements, each operation may bere-ordered, added, removed, or repeated.

Referring to method 1100 in more detail, at block 1102, the one or moreprocessing circuits can generate graphical user interfaces for each ofthe smart headsets. In various embodiments, each of the graphical userinterfaces is unique to each of the smart headsets and is based on atleast on one of a user preference or the sensor data (sometimes referredto herein as “IoT device data”). In some embodiments, each of thegraphical user interfaces can be configured to display content that canbe unique to each of the smart headsets and can be based on at least onone of a user preference or the sensor device data. The user preferencecan include size and color parameters of a user, and the one or moreprocessing circuits can be configured to adjust content displayed oneach of the graphical user interfaces. In some embodiments, theprocessing circuit can be configured to continuously update each of thegraphical user interfaces in real-time (e.g., update as shown in block1108 and 1110), such that the graphical user interfaces can include acombination of a set of views including content based on the sensordevice data, where each of the set of views includes a subset of views.Furthermore, set of views can include a table view and a plurality ofsmart headset views, and the subset of views can include a customerview, a provider view, and a manager view, and where each of the subsetof views includes different content unique to the individual.

At block 1104, the one or more processing circuits can provide thegraphical user interfaces to each of the smart headsets. In someembodiments, a mobile device associated with a customer configured toprovide authentication information of the customer to the interactivesurface. In various embodiments, providing the graphic user interface toeach of the smart headsets can be transferred over a network connection(e.g., wireless, communicably coupled, wired, direct wirelessconnection, network 154, and so on), and/or a pairing network (e.g.,Bluetooth™, NFC, hotspot, communicably coupled, and so on).

At block 1106, the one or more processing circuits can receive sensordevice data associated with at least one of biological data, behavioraldata, or a user input from at least one of the plurality of interactivesurface sensor devices or the plurality of smart headset sensor devices.In various embodiments, the interactive surface further includes amicrophone configured to convert sound input into an electrical signal.In some embodiments, the interactive surface can also include aplurality of IoT devices configured to receive various types of inputsuch as those described in detail with reference to smart table 106 inFIGS. 1A and 2A. In various embodiments, biological data or behaviordata is indicative of at least one of a user sentiment, a user emotion,a user attentiveness, a user gesture, a user preference, and any otherbiological or behavior indicator described herein. In variousembodiments, sensor data from one or more sensors (e.g., sometimesreferred to herein as input/output devices and/or IoT devices) can bereceived over a network connection (e.g., wireless, wired, communicablycoupled, direct wireless connection, network 154, and so on), and/or apairing network (e.g., Bluetooth™, NFC, hotspot, communicably coupled,and so on).

At block 1108, the one or more processing circuits can update, inresponse to receiving the sensor device data, a first graphical userinterface for a first smart headset of the smart headsets based on thesensor device data, wherein the first graphical user interface is uniqueto the first smart headset and is worn by a first individual. In someembodiments, the one or more processing circuits can continuously updateeach of the graphical user interfaces in real-time utilizing acombination of a set of views based on the sensor data, and wherein eachof the set of views includes a subset of views. That is, the set ofviews can include a table view and a plurality of smart headset viewsand the subset of views include a customer view, a provider view, and amanager view, and where each of the set of views and each of the subsetof views is personalized based on the individual. In variousembodiments, the table view can be a view of an environment that can bevisualized (e.g., by a user) without a smart headset (e.g., as shown inFIGS. 6-9 ) and a smart headset view can be a view of an environmentthat can be visualized (e.g., by the user) with a smart headset securedto a user's head and/or body. In one example, the one or more processingcircuits can receive, from the microphone, sound input from a customer,and update one or more of the graphical user interfaces for one or moreof the smart headsets based on the sound input. In some embodiments, thesubset of views are described in detail with reference to FIGS. 13-17 .

At block 1110, the one or more processing circuits can, update, inresponse to receiving the sensor device data, a second graphical userinterface for a second smart headset of the smart headsets based on thesensor device data, and wherein the second graphical user interface isunique to the second smart headset and is worn by a second individualdifferent than the first individual. In one example, the one or moreprocessing circuits can receive, from a camera, a blink from an employeeindicating a task has been approved (e.g., document, authentication, andso on). In another example, the one or more processing circuits canreceive, from a database system (e.g., governmental database, smarttable database 209, user device database 131, and so on), an Office ofForeign Assets Control (OFAC) alert and update a graphical userinterface of a manager indicated one or more users of a smart tableprovider session are associated with an OFAC alert. Accordingly, sensordata may be any data received from any system described herein. In someembodiments, the subset of views are described in detail with referenceto FIGS. 13-17 .

Referring now to FIG. 12 , an illustration of the smart table 106 andsmart headsets 195 of FIG. 1A including IoT devices 190 (sometimereferred to herein as “sensor devices”) in an environment 1200,according to example embodiments. In some embodiments, the environment1200 can include IoT devices 190A, 190B, 190C (described in detail withreference to FIG. 1A), one or more smart tables 106 (described in detailwith reference to FIGS. 1A and 1B), one or more smart headsets(described in detail with reference to FIG. 1A, 1B, and FIGS. 13-17 ),and one or more users 1205 and 1210 (e.g., people, customers, employees,managers, and so on). In one example, one or more processing circuits inthe environment 1200 (e.g., IoT devices 190, smart table 106, smartheadsets 195) can collect biological or behavioral data to performvarious actions associated with a smart table provider session.

Referring now generally to FIGS. 13-17 , illustrations of variousindividual views of the smart headset 195 of FIG. 1A, according toexample embodiments. Generally, various views can be a combination ofheadset display interfaces (e.g., on headset display 1301) overlaid onenvironment 1200 (e.g., smart table 106) during a smart table providersession. The headset display interfaces can include a plurality ofinterfaces (e.g., shared multi-dimensional graphical user interfaces)and objects overlaid on environment 1200 such that an individual (e.g.,a user or human operator) can provide biological data (e.g., stresslevel, heart rate, hand geometry, facial geometry, psyche, and so on)and/or behavioral data (e.g., haptic feedback, gesture, speech pattern,movement pattern (e.g., hand, food, arm, facial, iris, and so on),intangible feedback (e.g., selection of intangible content displayed onsmart headset 195), response to stimuli, and so on) to interact with theplurality of interfaces, objects, and/or environment 1200. For example,an individual may complete an action by selecting an object overlaid onenvironment 1200 (e.g., intangible object) with a hand gesture (e.g.,point at object). In another example, an individual may complete anaction by selecting at an object overlaid on environment 1200 with aneye movement (e.g., look at object). In yet another example, anindividual may provide their heart rate that may indicate a level ofstress. In yet another example, an individual may touch the smart table106 (e.g., haptic feedback) to provide input when completing a task(e.g., filling out a form, providing authentication information,pairing, and so on). In various embodiments, an individual may alsoreceive notifications (e.g., alerts, requests, status indicators, and soon) on the headset display interface, for example, indicating an actionto perform and/or current session information. Further, each view may beunique to an individual (e.g., customer view, employee view, managerview) such that each individual can view one or more different headsetdisplay interfaces overlaid on environment 1200 at any given time (e.g.,at the same time) during a smart table provider session. In variousembodiments, the smart headset 195 may be paired (e.g., Bluetooth™, NFC,wireless connection, wired connection, and so on) with the smart table106 and/or any computing system described herein.

Still referring generally to FIGS. 13-17 , each smart headset 195 caninclude a headset display (e.g., 1301, 1401, 1501, 1601, 1701). Theheadset display can be any suitable see-through display (sometimesreferred to as a “transparent display”) that utilizes any suitabletechnique to display a graphical user interface on the headset display.Various see-through displays can include, for example, a transparentscreen substrate fused with a liquid crystal technology (LCD), a lightfield display (LFD), a head-up display (HUD), a transparent screensubstrate fused with an organic light-emitting diode display (OLED), atransparent electroluminescent display (TASEL), and so on. Varioustechniques can include, for example, “Curved Mirror” (or “CurvedCombiner”) based, “Waveguide” (or “light-guide”) based, and so on. Invarious embodiments, the smart headset 195 may be of varying sizes, forexample, a helmet, a virtual reality headset, an augmented realityheadset, smart glasses, a hat, a headdress, and/or any type of headgear.In some embodiments, the headset display may be opaque (or a percentageopaque, sometimes referred to as “translucent”). Thus, the headsetdisplay and/or smart headset 195 is not limited to any specificcombination of hardware circuitry and software.

Still referring generally to FIGS. 13-17 , each view may include a toolicon (e.g., 1314, 1414, 1514, 1614, 1714) configured to enable a user ofthe smart headset 195 to customize the experience when interacting withthe smart headset 195. In various embodiments, when the tool icon isselected via a biological or behavioral action, it can enable a user toset specific arrangement and/or settings (e.g., colors, size,preferences, authentication procedure, and so on) when the sharedmulti-dimensional graphical user interface (collectively referred toherein as the “the headset display interface”) are shown on the headsetdisplay (e.g., 1301, 1401, 1501, 1601, 1701). For example, if a user iscolor blind, they may configure, via the tool icon, a smart headsetsetting such that any notifications displayed on the headset display arenot green or red. In another example, if a user has trouble with sightout of one eye, they may configure, via the tool icon, a smart headsetsetting such that one side of the headset display is favored overanother (e.g., for showing objects/content). In yet another example, auser could configure, via the tool icon, the size of text/objects of theheadset display interface. For example, improvements to traditionalcomputing system can include rearranging (sometimes referred to hereinas generating or modifying) content displayed on a first smart headsetdisplay based on a first user's preferences and environmental data andcan also rearrange (e.g., at the same time, in real-time) contentdisplayed on a second smart headset display based on a second user'spreferences and environmental data such that content can be rearrangeddifferently based on the user specific user utilizing a specific headsetwith particular preferences.

In some embodiments, each smart headset 195 (FIGS. 13-17 ) may includeone or more processing circuits that when executed can generate variousshared multi-dimensional graphical user interfaces. The smart headset195 can include one or more processors (e.g., any general purpose orspecial purpose processor), and include and/or be operably coupled toone or more transitory and/or non-transitory storage mediums and/ormemory devices (e.g., any computer-readable storage media, such as amagnetic storage, optical storage, flash storage, RAM, and so on)capable of providing one or more processors with program instructions.Instructions can include code from any suitable computer programminglanguage. The one or more processing circuits that when executed cangenerate various shared multi-dimensional graphical user interfaces. Insome embodiments, the smart headsets 195 may be headsets of varyingsizes integrated with integrated with various input/output devices(e.g., sensors, IoT devices, cameras). In various embodiments, smartheadset client application 238 of FIG. 2B can be configured to providethe multi-dimensional graphical user interfaces (e.g., personalizedviews) to each smart headset 195 to facilitate improved contentpresentation to various users of a smart table provider session (e.g.,customer, employee, manager, and so on) associated with each smart table106 and one or more smart headsets 195. Particularly, smart headsetclient application 238 is configured to communicate with the providercomputing system 102, the branch computing system 108, the user devices104, and the smart tables 106 to receive instructions and notificationsfrom the provider computing system 102, the branch computing system 104,smart tables 106, and/or IoT devices 190, provide and update thepersonalized views based on the received information, and performvarious tasks associated with a smart table provider session. Additionaldetails relating to the various individual views of the smart headset195 are provided herein with respect to FIGS. 14-17 .

Referring now to FIGS. 13A-13B in more detail. FIG. 13A is shown toinclude a plurality of graphical interface objects displayed on theheadset display 1301 including, an alert 1302 and a request 1304, and atool icon 1314. In this example, a customer may be wearing the smartheadset 195 and receiving the alert 1302 indicating an action should beperformed, and the notification 1304 indicating what type of actionshould be performed (e.g., enter PIN) (e.g., customer view). As shown,and collectively referred to herein, is the “customer view.” Further asshown, in the environment 1200, is a smart table 106 and a display 1310(e.g., touchscreen) displaying a request for the user to enter a PIN.Accordingly, the headset display 1301 notifies the customer utilizing avariety of notifications (e.g., alerts, request and/or statusindicators) to perform an action (e.g., enter your PIN) associated withthe smart table provider session. In one example, in response toreceiving the notifications, the customer may provide the PIN via averbalization. In a different example, in response to receiving thenotifications, the customer may provide the PIN via an intangiblekeyboard displayed on the headset display 1301.

FIG. 13B is shown to include a plurality of graphical interface objectsdisplayed on the headset display 1301 including, a request 1316 and atool icon 1314. In this example, an employee of a provider may bewearing the smart headset 195 and receiving the request 1316 (e.g.,“Customer Input”) indicating an action should be performed by a customer(e.g., shown in FIG. 13A) (e.g., employee view). As shown, andcollectively referred to herein, is the “employee view.” Further asshown, in the environment 1200, is a smart table 106 and a display 1310(e.g., touchscreen) displaying a request for the user to enter a PIN.Accordingly, the headset display 1301 notifies the employee utilizing avariety of notifications (e.g., alerts, request and/or statusindicators) to inform the customer to perform an action (e.g., entertheir PIN) associated with the smart table provider session. In oneexample, in response to receiving the notifications, the employee mayverbalize to the customer to enter their PIN.

Referring now to FIGS. 14A-14B in more detail. FIG. 14A is shown toinclude a plurality of graphical interface objects displayed on theheadset display 1401 including, alerts 1402 and 1418, and a tool icon1414. In this example, a customer may be wearing the smart headset 195and receiving the alerts (e.g., 1402, 1418) indicating cash isdispensing from the cash dispenser (e.g., dispenser management circuit216 of smart table 106 in FIG. 2A) (e.g., customer view). As shown, inthe environment 1200, is a smart table 106 that could dispense the cash.Accordingly, the headset display 1401 notifies the custom smart headset195 can include one or more processors ser utilizing a variety ofnotifications (e.g., alerts, request and/or status indicators) that cashis dispensing associated with the smart table provider session. In oneexample, in response to receiving the notifications, the customer maygrab the dispensed cash with their hand.

FIG. 14B is shown to include a plurality of graphical interface objectsdisplayed on the headset display 1401 including, an alert 1420, a closesession icon 1422, and a tool icon 1414. In this example, an employee ofa provider may be wearing the smart headset 195 and receiving the alerts(e.g., 1420) indicating that once the cash is dispensed to the customer,the employee should close the smart table provider session (e.g., byselecting the close session icon 1422, via intangible feedback) (e.g.,employee view). As shown, in the environment 1200, is a smart table 106that could dispense the cash. Accordingly, the headset display 1401notifies the employee utilizing a variety of notifications (e.g.,alerts, request and/or status indicators) that cash is dispensing andthat the smart table provider session should be closed. In variousembodiments, the determination that the session should be closed couldbe based on a variety of factors such as the actions previouslyperformed by the users of the smart table provider session, biologicaldata and/or behavioral data of the users during the smart table providersession, a time (e.g., time limit, current time, and so on), IoT devicedata (e.g., from the smart table 106, smart headset 195, and/or IoTdevices 190) the tasks completed by the users of the smart tableprovider session, and so on. In one example, in response to receivingthe notifications, the employee swipes left utilizing a hand gesture toclose the smart table provider session.

Referring now to FIGS. 15A-15B in more detail. FIG. 15A is shown toinclude a plurality of graphical interface objects displayed on theheadset display 1501 including, a request 1524, a magnification 1526,and a tool icon 1514. In this example, a customer may be wearing thesmart headset 195 and receiving the request 1524 indicating to providetheir legal name (e.g., customer view). As shown, in the environment1200, is a smart table 106 and a display 1528 displaying a loanapplication form. Accordingly, the headset display 1501 overlays themagnification 1526 on the loan application form emphasizing (e.g.,directing attention) to the customer to input their legal name here. Inone example, in response to receiving the notifications, the customermay provide a hand gesture (e.g., sign language) indicating their legalname. In various embodiments, other techniques can be utilized toemphasize content, such as, but not limited to, highlighting, bolding,underlining, arrows, hiding other content, and so on.

FIG. 15B is shown to include a plurality of graphical interface objectsdisplayed on the headset display 1501 including, a request 1530, analert 1532, and a tool icon 1514. In this example, an employee may bewearing the smart headset 195 and receiving the request 1530 (e.g.,“Customer Input”) indicating an action should be performed by a customer(e.g., shown in FIG. 15A) (e.g., employee view). As shown, in theenvironment 1200, is a smart table 106 and a display 1528 displaying aloan application form. Accordingly, the headset display 1301 overlaysthe alert 1532 (“Customer Viewing”) indicating the customer is viewing aparticular part of the display 1528. In one example, the employee maydetermine the customer has been viewing the legal name field for a longtime (e.g., 1 minute, 5 minutes, and so on) and subsequently ask thecustomer if they need any help. Further, the display 1528 is flipped inFIG. 15B (compared to FIG. 15A if the employee and customer are on twodifferent sides of the table as shown in FIG. 7 ) such that the employeecan view the loan application form in a formatted reading format (e.g.,reading up to down, left to right). More, the display 1528 does not showthe social security number (SSN) of the customer (e.g., limited access)such that customer and users that have access can only view the SSN. Invarious embodiments, each user of the smart table provider session mayinclude unique access such that each user can read (e.g., view) andwrite (e.g., perform actions) during a smart table provider sessionbased on the unique access. In some embodiments, each user may have anaccount that has a username and password such that each user of eachsmart table provider session logins to their account to start a smarttable provider session. Further, each user may have a specificauthorization level to perform specific action and view specific data.For example, an authorization level could be, but is not limited to,basic, medium, high, and top secret. In this example, a basicauthorization level may be required when a customer requests to check anaccount balance; a medium authorization level may be required when acustomer requests to change their address and/or remove a joint ownerfrom an account; a high authorization level may be required when acustomer requests to apply for a home loan; and a top authorizationlevel may be required when a customer requests to close their accountand wire the remaining balance to another account.

Referring now to FIGS. 16A-16B in more detail. FIG. 16A is shown toinclude a plurality of graphical interface objects displayed on theheadset display 1601 including, a status indicator 1634, a request 1638,and a tool icon 1614. In this example, a customer may be wearing thesmart headset 195 and receiving the request 1638 indicating to providethe state the customer resides in (e.g., customer view). As shown, inthe environment 1200, is a smart table 106 and a display 1636 displayinga credit card application. Accordingly, the headset display 1601overlays the request 1638 (“Tell us the state you reside”) requestingthe customer to input the state they reside in. Further, the headsetdisplay 1601 also indicates the percentage completed of the credit cardapplication (e.g., 60%). In one example, in response to receiving thenotifications, an input/output device (e.g., 240) of the smart headset195 may detect and interpret brain wave patterns (e.g., usingelectroencephalography (EEG), also known as mind reading) to fill in thestate of residency of the customer. In another example, a camera in theenvironment (e.g., as shown in FIG. 12 ) may record the facial movementsof the customer to analyze and fill in the state of residency of thecustomer.

FIG. 16B is shown to include a plurality of graphical interface objectsdisplayed on the headset display 1601 including, a status indicator1638, an alert 1640, and a tool icon 1614. In this example, an employeemay be wearing the smart headset 195, receiving the alert 1640indicating the customer is becoming frustrated (e.g., level of stress),and shown the status indicator 1638 (e.g., various colors given forvarious statuses) indicating the customers current status (e.g., red isstressed, green is happy, yellow is undetermined, and so on) (e.g.,employee view). As shown, in the environment 1200, is a smart table 106and a display 1636 displaying a credit card application. In one example,in response to receiving the notifications and a determination that thecustomer is frustrated, the employee may override the customer and fillin the credit card application instead of the customer. In anotherexample, in response to receiving the notifications and a determinationthat the customer is frustrated, a cup of water may be automaticallyfilled and presented to the customer via an input/output device (e.g.,220) of the smart table 106 (e.g., automatic water dispenser).

Referring now to FIGS. 17A-17F in more detail. Each of FIGS. 17A-17F areshown to include a sub-view menu display, displayed on the headsetdisplay 1701 including a plurality of sub-views that can include aplurality of statistics regarding various sessions. For example,sub-views can include, but not limited to, a stress level sub-view 1742,a completion percentage sub-view 1744, a session task sub-view 1746, asession audio sub-view 1748, a metrics sub-view 1750, an administrativesub-view 1752. In some embodiments, statistics can include stress level,completion percentage, employees' cognitive ability, session elapsedtime, other various session statistics over a period of time (e.g.,current session, one hour, one day, one week, one month, and so on), andso on. In one example, the one or more processors of the smart headset195 can determine and/or track how much memory (e.g., statistic) hasbeen allocated to various tasks and notifications displayed on theheadset display 1701. In this example, the one or more processors of thesmart headset 195 can adjust the various tasks and notifications basedon how much memory has been allocated (e.g., unselect certainconfigurations, remagnify, demagnify, remove certain tasks and/ornotifications) such that the one or more processors are activelytracking memory usage throughout sessions.

In various embodiments, various users may have access to the side menudisplay (e.g., manager, chief operating officer (CEO), auditor,administrator, supervisor, principal, and so on). As shown, andcollectively referred to herein, is the “manager view.” Further asshown, in the environment 1200, is a plurality of smart tables 106 witha plurality of individuals, where each individual may be paired with asmart headset 195 and/or smart table 106 and may be in an active smarttable provider session.

FIG. 17A is shown to include a plurality of graphical interface objectsdisplayed on the headset display 1701 including, a sub-view menu (e.g.,1742, 1744, 1746, 1748, 1750, 1752), an alert 1754, a plurality ofcompletion percentage alerts (e.g., 1756, 1758, 1760), and a tool icon1714. In this example, a manager may be wearing the smart headset 195and selected the completion percentage sub-view 1744, such that eachsmart table provider session (e.g., three shown) is indicated with thepercentage completed of a task and/or session. As shown, completionpercentage alert 1756 does not include a percentage and instead displaysa mid-session review alert that could be indicative of a 50% completion.The alert 1754 may also indicate an action is to be performed by themanager (e.g., review the current smart table provider session). Also asshown, in the environment 1200, is a plurality of smart tables 106. Inone example, in response to receiving the notifications, the manager maytravel to the smart table associated with the alert 1754 and perform areview (e.g., as described in detail with reference to FIG. 17F). Invarious embodiments, the completion percentage may be determined basedon the progress of the current task and/or smart table provider session.

FIG. 17B is shown to include a plurality of graphical interface objectsdisplayed on the headset display 1701 including, a sub-view menu (e.g.,1742, 1744, 1746, 1748, 1750, 1752), alerts 1762A, 1762B, and 1762C(collectively referred to herein as “alerts 1762”), alerts 1764A and1764B, alert 1766, and a tool icon 1714. In this example, a manager maybe wearing the smart headset 195 and selected the stress level sub-view1742, such that each smart table provider session (e.g., three shown) isindicated with a stress level (e.g., alerts 1762) and each individual isdesignated a user type (e.g., alerts 1764A and 1764B), such as, customer(C), employee (E), and so on. The alert 1766 may also indicate an actionis to be performed by the manager (e.g., mitigate stress). Also asshown, in the environment 1200, is a plurality of smart tables 106. Inone example, in response to manager analyzing the environment 1200, themanager may step into smart table provider session associated with thealert 1766 to help mitigate stress. In various embodiments, stress leveland user types may be determined (e.g., by a processor) based onretrieving various input/output devices (e.g., 122, 152, 134, 220, 240,190, and so on).

FIG. 17C is shown to include a plurality of graphical interface objectsdisplayed on the headset display 1701 including, a sub-view menu (e.g.,1742, 1744, 1746, 1748, 1750, 1752), an alert 1768, and a completionpercentage alert 1770. In this example, a manager may be wearing thesmart headset 195 and selected the completion percentage sub-view 1744and the session task sub-view 1746, such that each smart table providersession (e.g., three shown) is indicated with the percentage completedof a task and/or session and the task currently being completed (e.g.,loan app, check deposit, card application, and so on). Also as shown, inthe environment 1200, is a plurality of smart tables 106. In oneexample, in response to receiving the notifications, the manager mayschedule a waiting customer to utilize the smart table 106 associatedwith the highest completion percentage (e.g., 75%) once the smart tableprovider session is completed.

FIG. 17D is shown to include a plurality of graphical interface objectsdisplayed on the headset display 1701 including, a sub-view menu (e.g.,1742, 1744, 1746, 1748, 1750, 1752), audio connections 1772A, 1772B, and1772C (collectively referred to herein as “audio connections 1772”), anda tool icon 1714. In this example, a manager may be wearing the smartheadset 195 and selected the session audio sub-view 1748, such that eachsmart table provider session (e.g., three shown) includes an overlayaudio connections 1772 overlaid above the smart table 106. Also asshown, in the environment 1200, is a plurality of smart tables 106. Inone example, in response to selecting audio connection 1772A, themanager may listen (e.g., audio) in on the conversation currentlyoccurring during the smart table provider session. In variousembodiments, the audio of the conversation may be retrieved (e.g., by aprocessor) from various input/output devices (e.g., 122, 152, 134, 220,240, 190, and so on). In various embodiments, the audio can be saved(e.g., stored in smart table database 209 and/or smart headset database229) for utilization in artificial intelligence (AI) analysis in thefuture. In one example, the audio saved can be utilized as input into anAI model and an output prediction can include a transaction of the audiosaved. In this example, the transaction could be utilized to determinestress level (e.g., trigger words (e.g., “whatever,” “I'm annoyed,” andso on), emotional words (“I cannot wait till I'm done today,” “I'm nothaving a good day,” and so on), current session progress (e.g., 50%complete since the checks were printed and individual said “here areyour checks,” 100% complete since an individual said “have a nice day,”progress went from 45% to 25% because an individual said “lets retrythat,” and so on), and/or employees' cognitive ability (e.g., slurringwords, talking slow, mispronouncing words, and so on), and so on.

In various embodiments, previously collected IoT device data (e.g.,audio files, images, recording, any other IoT device data, and so on)can be used to train a machine-learning model. That is, predictionsregarding smart table provider sessions could be based on artificialintelligence or a machine-learning model. For example, a firstmachine-learning model may be trained to identify particular biometricsamples (e.g., fingerprint, face, hand) and output a prediction. In thisexample, a second machine-learning model may be trained to identify toparticular individual based on the audio of their voice. In otherexamples, a machine-learning model may be trained to stitch presenteddocuments and perform obstruction removal (e.g., hand, head, foot, andso on) associated with a smart table provider session. In variousarrangements, authenticating the user and/or performing various actionsin a smart table provider session may include utilizing a machinelearning algorithm (e.g., a neural network, convolutional neuralnetwork, recurrent neural network, linear regression model, and sparsevector machine). The various computing systems/devices described hereincan input various data (e.g., biological, behavioral, biometric,geographic, IoT device data and so on) into the machine learning model,and receive an output from the model indicating a particular action toperform (by the processing circuit, for example, 112, 126, 138, 204,224). In one example, IoT device data may be inputted into the model andthe output prediction may be a stress level prediction of a user, towhich the stress level is displayed (e.g., graphical user interfaceupdated) to a user in a view (e.g., manager view).

FIG. 17E is shown to include a plurality of graphical interface objectsdisplayed on the headset display 1701 including, a sub-view menu (e.g.,1742, 1744, 1746, 1748, 1750, 1752), status indicators 1778A, 1778B,1778C (collectively referred to herein as “status indicators 1778”), andvarious metric alerts (e.g., 1774A, 1774B, 1774C, 1776A, 1776B, 1776C,1780A, 1780B, and 1780C), and a tool icon 1714. In this example, amanager may be wearing the smart headset 195 and selected the metricssub-view 1750, such that each smart table provider session (e.g., threeshown) indicates various metrics. As shown, various metrics includes,but not limited to, a current session time (e.g., 1780A, 1780B,1780C—how long the smart table provider session has occurred), anemployees' cognitive ability (e.g., 1776A, 1776B, 1776C—mentalcapability to perform tasks), and each employees shift start, and endtime (e.g., 1774A, 1774B, 1774C). The alert 1754 may also indicate anaction is to be performed by the manager (e.g., review the current smarttable provider session). Also as shown, in the environment 1200, is aplurality of smart tables 106. Further as shown, and with reference toFIG. 16B, is status indicators 1778 indicative of a variety ofproperties associated with a smart table provider session (e.g., levelof stress, completion percentage (e.g., 0%-40% is red, 41%-89% isyellow, and 90%-100% is green), session time (e.g., below 10 minutes isgreen, between 10-20 minutes is yellow, and above 20 minutes is red). Inone example, in response to receiving the notifications, the manager maytravel to the smart table where an employee's cognitive ability (e.g.,1776C) is deteriorating (e.g., falling below a threshold) and ask theemployee to take a break such the manager can finish the smart tableprovider session. In another example, in response to a yellow statusindicator (e.g., 1778A) indicating the time of session is longer than anormal session, the manager may intervene and determine the cause forthe longer than normal session. In various embodiments, the cognitiveability, current session time may be determined (e.g., by a processor)based on retrieving various input/output devices (e.g., 122, 152, 134,220, 240, 190). In various embodiments, the shift start, and end timemay be determined (e.g., by a processor) based on retrieving data fromvarious sources (e.g., 102, 104, 108, 195, 106, 190, and so on). In someembodiments, the one or more processing circuits of the variouscomputing systems/devices described herein automatically (e.g., inreal-time) send notifications to various users of smart table providersessions.

In various embodiments, the headset display 1701 can incorporatehistorical data from previous sessions regarding an individual or acollections of individuals. For example, the previous levels of stress(e.g., stored in smart table database 209 and/or smart headset database229) of a specific individual can be utilized to calculate a currentstress level of the specific individual. In this example, differentweights (e.g., 0.25, 0.75) can be associated with historical data suchthat levels of stress can be calculated by incorporating current stress(e.g., with a factor of 0.75) and previous stress (e.g., with a factorof 0.25) such that an overall stress level can be calculated. In thisexample, if stress level was a scale between zero and a hundred and thecurrent stress level was 82 and the previous stress level (e.g., for thelast 7 days) was 56, the level of stress would be 75.5 (e.g.,((82×0.75)+(56×0.25))=61.5+14.0=75.5). In other examples, various othercalculations and factors may be utilized to calculate various statisticsutilizing various data (e.g., current and/or historical).

FIG. 17F is shown to include a plurality of graphical interface objectsdisplayed on the headset display 1701 including, a sub-view menu (e.g.,1742, 1744, 1746, 1748, 1750, 1752), a request 1782, requests 1786A and1786B, an alert 1784, and a tool icon 1714. In this example, a managermay be wearing the smart headset 195 and selected the administrativesub-view 1752 (e.g., in response to intervening in a smart tableprovider session), such that each smart table provider session (e.g.,one shown) can include an administrative view (referred to herein as“admin view”) such that elevated access is provided to perform tasksthat may not be able to be performed by some users. In some embodiments,one or more processing circuits may log each action performed in theadmin view (e.g., for auditing purposes) and each time the admin view isviewed, a user may be required to authenticate themselves (e.g., using ausername and password, biometric, user device, and so on). As shown,request 1782 indicates the manager should confirm the tax ID of thecustomer (e.g., with reference to FIGS. 16A and 16B). Also as shown, toconfirm the tax ID, the manager may select one of the requests 1786A or1786B indicating the tax ID is correct or it is incorrect. Also asshown, in the environment 1200, is a smart table 106 and a display 1788(e.g., touchscreen) displaying a credit card application. Accordingly,the headset display 1701 overlays the request 1786A and 1768B requestingthe manager to indicate if the tax ID is correct. In one example, inresponse to the manager reviewing the tax ID, the manager may providethe indication of correctness via a verbalization. In a differentexample, in response to the manager reviewing the tax ID, the managermay provide a selection via the intangible button displayed on theheadset display 1701.

Referring now to FIG. 18 , an illustration of the smart table 106 andsmart headsets 195 of FIG. 1A in the environment 1200 (with reference toFIG. 12 above), according to example embodiments. The user is shownproviding intangible feedback by completing a selection of objects shownon the display of the smart headset 195. Accordingly, the user of asmart headset 195 before, during, or after, a smart table providersession can complete selections of objects based on the retrievingand/or receiving (e.g., by a processor) data from various input/outputdevices (e.g., 122, 152, 134, 220, 240, 190, and so on) indicating aselection occurred (e.g., raise hand and point, wave hand, kick foot,nod head, and so on, with reference to FIGS. 13-17 shown above).

The embodiments described herein have been described with reference todrawings. The drawings illustrate certain details of specificembodiments that provide the systems, methods and programs describedherein. However, describing the embodiments with drawings should not beconstrued as imposing on the disclosure any limitations that may bepresent in the drawings.

It should be understood that no claim element herein is to be construedunder the provisions of 35 U.S.C.§ 112(f), unless the element isexpressly recited using the phrase “means for.”

As used herein, the term “circuitry” may include hardware structured toexecute the functions described herein. In some embodiments, eachrespective “circuit” may include machine-readable media for configuringthe hardware to execute the functions described herein. The circuit maybe embodied as one or more circuitry components including, but notlimited to, processing circuitry, network interfaces, peripheraldevices, input devices, output devices, sensors, etc. In someembodiments, a circuit may take the form of one or more analog circuits,electronic circuits (e.g., integrated circuits (IC), discrete circuits,system on a chip (SOCs) circuits, etc.), telecommunication circuits,hybrid circuits, and any other type of “circuit.” In this regard, the“circuit” may include any type of component for accomplishing orfacilitating achievement of the operations described herein. Forexample, a circuit as described herein may include one or moretransistors, logic gates (e.g., NAND, AND, NOR, OR, XOR, NOT, XNOR,etc.), resistors, multiplexers, registers, capacitors, inductors,diodes, wiring, and so on).

The “circuit” may also include one or more processors communicativelycoupled to one or more memory or memory devices. In this regard, the oneor more processors may execute instructions stored in the memory or mayexecute instructions otherwise accessible to the one or more processors.In some embodiments, the one or more processors may be embodied invarious ways. The one or more processors may be constructed in a mannersufficient to perform at least the operations described herein. In someembodiments, the one or more processors may be shared by multiplecircuits (e.g., circuit A and circuit B may comprise or otherwise sharethe same processor which, in some example embodiments, may executeinstructions stored, or otherwise accessed, via different areas ofmemory).

Alternatively or additionally, the one or more processors may bestructured to perform or otherwise execute certain operationsindependent of one or more co-processors. In other example embodiments,two or more processors may be coupled via a bus to enable independent,parallel, pipelined, or multi-threaded instruction execution. Eachprocessor may be provided as one or more general-purpose processors,application specific integrated circuits (ASICs), field programmablegate arrays (FPGAs), digital signal processors (DSPs), or other suitableelectronic data processing components structured to execute instructionsprovided by memory. The one or more processors may take the form of asingle core processor, multi-core processor (e.g., a dual coreprocessor, triple core processor, quad core processor, etc.),microprocessor, etc. In some embodiments, the one or more processors maybe external to the apparatus, for example the one or more processors maybe a remote processor (e.g., a cloud based processor). Alternatively oradditionally, the one or more processors may be internal and/or local tothe apparatus. In this regard, a given circuit or components thereof maybe disposed locally (e.g., as part of a local server, a local computingsystem, etc.) or remotely (e.g., as part of a remote server such as acloud based server). To that end, a “circuit” as described herein mayinclude components that are distributed across one or more locations.

Example systems and devices in various embodiments might include aprocessing unit, a system memory, and a system bus that couples varioussystem components including the system memory to the processing unit.Each memory device may include non-transient volatile storage media,non-volatile storage media, non-transitory storage media (e.g., one ormore volatile and/or non-volatile memories), etc. In some embodiments,the non-volatile media may take the form of ROM, flash memory (e.g.,flash memory such as NAND, 3D NAND, NOR, 3D NOR, etc.), EEPROM, MRAM,magnetic storage, hard discs, optical discs, etc. In other embodiments,the volatile storage media may take the form of RAM, TRAM, ZRAM, etc.Combinations of the above are also included within the scope ofmachine-readable media. In this regard, machine-executable instructionscomprise, for example, instructions and data which cause a generalpurpose computer, special purpose computer, or special purposeprocessing machines to perform a certain function or group of functions.Each respective memory device may be operable to maintain or otherwisestore information relating to the operations performed by one or moreassociated circuits, including processor instructions and related data(e.g., database components, object code components, script components,etc.), in accordance with the example embodiments described herein.

It should also be noted that the term “input devices,” as describedherein, may include any type of input device including, but not limitedto, a keyboard, a keypad, a mouse, joystick or other input devicesperforming a similar function. Comparatively, the term “output device,”as described herein, may include any type of output device including,but not limited to, a computer monitor, printer, facsimile machine, orother output devices performing a similar function.

Any foregoing references to currency or funds are intended to includefiat currencies, non-fiat currencies (e.g., precious metals), andmath-based currencies (often referred to as cryptocurrencies). Examplesof math-based currencies include Bitcoin, Litecoin, Dogecoin, and thelike.

It should be noted that although the diagrams herein may show a specificorder and composition of method steps, it is understood that the orderof these steps may differ from what is depicted. For example, two ormore steps may be performed concurrently or with partial concurrence.Also, some method steps that are performed as discrete steps may becombined, steps being performed as a combined step may be separated intodiscrete steps, the sequence of certain processes may be reversed orotherwise varied, and the nature or number of discrete processes may bealtered or varied. The order or sequence of any element or apparatus maybe varied or substituted according to alternative embodiments.Accordingly, all such modifications are intended to be included withinthe scope of the present disclosure as defined in the appended claims.Such variations will depend on the machine-readable media and hardwaresystems chosen and on designer choice. It is understood that all suchvariations are within the scope of the disclosure. Likewise, softwareand web implementations of the smart table system may be accomplishedwith standard programming techniques with rule based logic and otherlogic to accomplish the various database searching steps, correlationsteps, comparison steps and decision steps.

The foregoing description of embodiments has been presented for purposesof illustration and description. It is not intended to be exhaustive orto limit the disclosure to the precise form disclosed, and modificationsand variations are possible in light of the above teachings or may beacquired from this disclosure. The embodiments were chosen and describedin order to explain the principals of the disclosure and its practicalapplication to enable one skilled in the art to utilize the variousembodiments and with various modifications as are suited to theparticular use contemplated. Other substitutions, modifications, changesand omissions may be made in the design, operating conditions andarrangement of the embodiments without departing from the scope of thepresent disclosure as expressed in the appended claims.

What is claimed is:
 1. A smart table system comprising: an interactivesurface of a smart table comprising: a touchscreen; and a plurality ofinteractive surface sensor devices; a plurality of smart headsetscomprising: a transparent display; a plurality of smart headset sensordevices, each of the smart headsets configured to be respectively wornby an individual; a processing circuit configured to: detect a sessiontrigger event based on detecting a first user device is within awireless communication range of the smart table system; in response tothe session trigger event, provide an indication to the first userdevice on which smart headset of the plurality of smart headsets towear; initiate a user session based on detecting the session triggerevent, wherein initiating the user session comprises authenticating aplurality of user devices and pairing each of the plurality of userdevices with the smart table, wherein the user session is between acustomer of a provider with the first user device of the plurality ofuser devices and an employee of the provider with a second user deviceof the plurality of user devices, and wherein the user session comprisesestablishing communication between the plurality of smart headsets, thesmart table, the plurality of user devices, and the processing circuit;determine a level of authentication associated with the customer basedon authenticating the first user device; update the interactive surfaceindicating successful pairing of the plurality of user devices with thesmart table; generate, in response to initiating the user session,graphical user interfaces for each of the smart headsets, wherein atleast one graphical user interface of the graphical user interfaces isgenerated based on the level of authentication; provide the graphicaluser interfaces to each of the smart headsets; receive sensor devicedata associated with at least one of biological data, behavioral data,or a user input from at least one of the plurality of interactivesurface sensor devices or the plurality of smart headset sensor devices;monitor, during the user session, biometric data of at least oneindividual wearing at least one of the plurality of smart headsets;update, in response to receiving the sensor device data and monitoringthe biometric data of the at least one individual during the usersession, a first graphical user interface for a first smart headset ofthe smart headsets based on the sensor device data, wherein the firstgraphical user interface unique to the first smart headset and is wornby a first individual, and wherein the updated first graphical userinterface comprises a first alert or request displayed on thetransparent display of the first smart headset; update, in response toreceiving the sensor device data and monitoring the biometric data ofthe at least one individual during the user session, a second graphicaluser interface for a second smart headset of the smart headsets based onthe sensor device data, and wherein the second graphical user interfaceunique to the second smart headset and is worn by a second individualdifferent than the first individual, and wherein the updated secondgraphical user interface comprises a second alert or request displayedon the transparent display of the second smart headset; and wherein theupdating the first graphical user interface and the second graphicaluser interface occurs simultaneously during the user session, andwherein the first graphical user interface and the second graphical userinterface share a graphical interface object, and wherein the updatingof the first graphical user interface and the second graphical userinterface comprises updating the first alert or request on the firstgraphical user interface and updating the second alert or request on thesecond graphical user interface.
 2. The smart table system of claim 1,wherein each of the first graphical user interface and the secondgraphical user interface is configured to display content that is uniqueto each of the smart headsets and is based on at least on one of a userpreference or the sensor device data.
 3. The smart table system of claim2, wherein the user preference comprises size and color parameters of auser, and wherein the processing circuit is configured to adjust thecontent displayed on each of the first graphical user interface and thesecond graphical user interface.
 4. The smart table system of claim 1,wherein the processing circuit is configured to continuously update eachof the first graphical user interface and the second graphical userinterface in real-time, the first graphical user interface and thesecond graphical user interface comprising a combination of a set ofviews comprising content based on the sensor device data, wherein eachof the set of views comprises a subset of views.
 5. The smart tablesystem of claim 4, wherein the set of views comprise a table view and aplurality of smart headset views, and the subset of views comprises acustomer view, a provider view, and a manager view, and wherein each ofthe subset of views comprises different content unique to theindividual.
 6. The smart table system of claim 1, wherein the processingcircuit is further configured to: receive, from a microphone, soundinput from the customer, wherein the customer is the first individual;and update the first graphical user interface of the first smart headsetof the smart headsets based on the sound input, wherein the firstgraphical user interface update comprises updating first content of thefirst graphical user interface; update the second graphical userinterface of the second smart headset of the smart headsets based on thesound input, wherein the second graphical user interface updatecomprises updating second content of the second graphical user interfacedifferent from the first content.
 7. The smart table system of claim 1,wherein the first user device is configured to communicate over anetwork with a network circuit of the smart table system and to provideauthentication information of the customer to the network circuit,wherein the authentication information is at least one of a customerpassword, the biometric data, or a geometric information.
 8. The smarttable system of claim 1, wherein the biological data, the behavioraldata, or the user input is indicative of at least one of a usersentiment, a user emotion, a user attentiveness, a user gesture, or auser preference.
 9. A smart table system comprising: a plurality ofdevices comprising a camera, a microphone, and a stress sensor, eachdevice configured to collect first device data; a plurality of smartheadsets comprising a transparent display and coupled to a plurality ofsmart headset sensor devices, the smart headset sensor devicesconfigured to collect second device data, wherein the second device datais smart headset sensor device data, and each of the smart headsets areconfigured to be worn by an individual; an interactive surface of asmart table comprising a touchscreen; and a processing circuitconfigured to: detect a session trigger event based on detecting a firstuser device is within a wireless communication range of the smart tablesystem; initiate a user session based on detecting the session triggerevent, wherein initiating the user session comprises authenticating aplurality of user devices and pairing each of the plurality of userdevices with the smart table, wherein the user session is between acustomer of a provider with the first user device of the plurality ofuser devices and an employee of the provider with a second user deviceof the plurality of user devices, and wherein the user session comprisesestablishing communication between the plurality of smart headsets, thesmart table, the plurality of user devices, and the processing circuit;update the interactive surface indicating successful pairing of theplurality of user devices with the smart table; generate, in response toinitiating the user session, graphical user interfaces for each of thesmart headsets; provide the graphical user interfaces to a respectivesmart headset; monitor, during the user session, biometric data of atleast one individual wearing at least one of the plurality of smartheadsets; update a first graphical user interface of the graphical userinterfaces for a first smart headset of the smart headsets based on thefirst device data or the second device data, and wherein the updatedfirst graphical user interface comprises a first alert or requestdisplayed on the transparent display of the first smart headset; updatea second graphical user interface of the graphical user interfaces for asecond smart headset of the smart headsets based on the first devicedata or the second device data, and wherein the updated second graphicaluser interface comprises a second alert or request displayed on thetransparent display of the second smart headset; and wherein the firstgraphical user interface is unique to the first smart headset and isworn by a first individual, and wherein the second graphical userinterface is unique to the second smart headset and is worn by a secondindividual different than the first individual, and wherein the updatingthe first graphical user interface and the second graphical userinterface occurs simultaneously during the user session, and wherein thefirst graphical user interface and the second graphical user interfaceshare a graphical interface object, and wherein the updating of thefirst graphical user interface and the second graphical user interfacecomprises updating the first alert or request on the first graphicaluser interface and updating the second alert or request on the secondgraphical user interface.
 10. The smart table system of claim 9, whereineach of the first graphical user interface and the second graphical userinterface is configured to display content that is unique to each of thesmart headsets and is based on at least one of a user preference, thefirst device data, or the second device data.
 11. The smart table systemof claim 9, wherein the processing circuit is configured to continuouslyupdate each of the first graphical user interface and the secondgraphical user interface in real-time, the first graphical userinterface and the second graphical user interface comprising acombination of a set of views comprising content based on the firstdevice data and the second device data, wherein each of the set of viewscomprises a subset of views.
 12. The smart table system of claim 9,wherein the first user device is configured to communicate over anetwork with a network circuit of the smart table system, and configuredto provide authentication information of the customer to the networkcircuit, wherein the authentication information is at least one of acustomer password, the biometric data, or a geometric information.
 13. Asmart table system comprising: a processing circuit configured to:detect a session trigger event based on detecting a first user device iswithin a wireless communication range of the smart table system;initiate a user session with a smart table based on detecting thesession trigger event, wherein initiating the user session comprisesauthenticating a plurality of user devices and pairing each of theplurality of user devices with the smart table, wherein the smart tablecomprises an interactive surface comprising a touchscreen and aplurality of interactive surface sensors, wherein the user session isbetween a customer of a provider with the first user device of theplurality of user devices and an employee of the provider with a seconduser device of the plurality of user devices, and wherein the usersession comprises establishing communication between a plurality ofsmart headsets, the smart table, the plurality of user devices, and theprocessing circuit; update the interactive surface indicating successfulpairing of the plurality of user devices with the smart table; generate,in response to initiating the user session, graphical user interfacesfor the plurality of the smart headsets, each of the smart headsetscomprising a transparent display and a plurality of smart headsetsensors, each of the smart headsets configured to be worn by anindividual; provide the graphical user interfaces to each of the smartheadsets; receive sensor data associated with at least one of biologicaldata, behavioral data, or a user input from at least one of theplurality of interactive surface sensors or the plurality of smartheadset sensors; monitor, during the user session, biometric data of atleast one individual wearing at least one of the plurality of smartheadsets; in response to receiving the sensor data and monitoring thebiometric data of the at least one individual during the user session,update a first graphical user interface for a first smart headset of thesmart headsets based on the sensor data, wherein the first graphicaluser interface is unique to the first smart headset and is worn by afirst individual, and wherein the updated first graphical user interfacecomprises a first alert or request displayed on the transparent displayof the first smart headset; in response to receiving the sensor data andmonitoring the biometric data of the at least one individual during theuser session, update a second graphical user interface for a secondsmart headset of the smart headsets based on the sensor data, andwherein the second graphical user interface is unique to the secondsmart headset and is worn by a second individual different than thefirst individual, and wherein the updated second graphical userinterface comprises a second alert or request displayed on thetransparent display of the second smart headset; and wherein theupdating the first graphical user interface and the second graphicaluser interface occurs simultaneously during the user session, andwherein the first graphical user interface and the second graphical userinterface share a graphical interface object, and wherein the updatingof the first graphical user interface and the second graphical userinterface comprises updating the first alert or request on the firstgraphical user interface and updating the second alert or request on thesecond graphical user interface.
 14. The smart table system of claim 13,wherein each of the first graphical user interface and the secondgraphical user interface is configured to display content that is uniqueto each of the smart headsets and is based on at least on one of a userpreference or the sensor data.
 15. The smart table system of claim 14,wherein the user preference comprises size and color parameters of auser, and wherein the processing circuit is configured to adjust thecontent displayed on each of the first graphical user interface and thesecond graphical user interface.
 16. The smart table system of claim 13,wherein the processing circuit is configured to continuously update eachof the first graphical user interface and the second graphical userinterface in real-time, the graphical user interfaces comprising acombination of a set of views comprising content based on the sensordata, wherein each of the set of views comprises a subset of views. 17.The smart table system of claim 16, wherein the set of views comprise atable view and a plurality of smart headset views, and the subset ofviews comprise a customer view, a provider view, and a manager view, andwherein each of the set of views and each of the subset of viewscomprises different content unique to the individual.
 18. The smarttable system of claim 13, wherein the processing circuit is furtherconfigured to: receive, from a microphone, sound input from thecustomer, wherein the customer is the first individual; and update thefirst graphical user interface of the first smart headset of the smartheadsets based on the sound input, wherein the first graphical userinterface update comprises updating first content of the first graphicaluser interface; update the second graphical user interface of the secondsmart headset of the smart headsets based on the sound input, whereinthe second graphical user interface update comprises updating secondcontent of the second graphical user interface different from the firstcontent.
 19. The smart table system of claim 13, wherein the first userdevice is configured to communicate over a network with a networkcircuit of the smart table system and configured to provideauthentication information of the customer to the network circuit,wherein the authentication information is at least one of a customerpassword, the biometric data, or a geometric information.
 20. The smarttable system of claim 13, wherein the biological data, the behavioraldata, or the user input is indicative of at least one of a usersentiment, a user emotion, a user attentiveness, a user gesture, or auser preference.